Notion MCP can let Aurora search and retrieve fundraising knowledge the connected user is authorized to access. Finta can turn that source material into an evidence ledger, identify conflicting or stale claims, and prepare a consistent investor memo or update.
The relationship-intelligence value is knowing which context should shape the next investor conversation, not simply searching a workspace. Finta's current catalog still uses Notion's supported legacy SSE endpoint. Notion now prefers Streamable HTTP at https://mcp.notion.com/mcp, so the page should explain the current state and the required remediation instead of claiming the preferred connection has been verified.
Current status
| Connection detail | Current evidence |
|---|---|
| Connection model | Catalog MCP |
| Official preferred server | https://mcp.notion.com/mcp |
| Official preferred transport | Streamable HTTP |
| Current Finta server | https://mcp.notion.com/sse |
| Current Finta transport | Legacy SSE |
| Official authentication | Interactive Notion user OAuth |
| Repository configuration | Present but stale on August 22, 2026 |
| Authenticated Notion connection | Pending endpoint remediation |
| Live tools/list receipt | Pending |
| Known page read | Pending |
| Controlled file upload and cleanup | Pending |
Notion continues to document https://mcp.notion.com/sse as a legacy fallback, but new configuration should use https://mcp.notion.com/mcp with Streamable HTTP.
The prior Finta page claim that Notion MCP does not support file uploads is stale and must not be repeated. Notion now documents notion-create-file-upload for a single-part local file up to twenty MiB, plus attachment tools. This is provider documentation, not proof of a completed upload through Finta.
The hosted Notion MCP server uses interactive user OAuth. Do not publish a headless bearer-token setup for this connection.
What is documented and what Finta verified
The following tools are documented by Notion for its hosted MCP server. Availability varies by plan, permission, and current_tool_access. Exact tools exposed to Finta remain pending until endpoint remediation, OAuth, and live tools/list discovery are complete.
| Tool or capability | Purpose | Finta evidence |
|---|---|---|
| notion-search | Search authorized Notion content and eligible connected sources | Provider-documented; connected-source search can require Notion AI |
| notion-fetch | Fetch pages, databases, users, workspace context, and current_tool_access | Provider-documented; should anchor safe verification |
| notion-create-file-upload | Upload a local file using the documented single-part flow | Provider-documented up to twenty MiB; live Finta upload pending |
| notion-create-attachment | Create a supported attachment | Provider-documented; live Finta discovery pending |
| notion-download-attachment | Download supported UTF-8 text attachments | Provider-documented with current size and content limits; not a general binary-download claim |
| notion-create-pages | Create pages | Provider-documented write; keep disabled until controlled verification |
| notion-update-page | Update a page | Provider-documented write; keep disabled until controlled verification |
| notion-convert-page-to-skill | Convert supported page content into a reusable skill | Provider-documented; live Finta discovery pending |
| notion-move-pages | Move pages | Provider-documented write; keep disabled until controlled verification |
| notion-duplicate-page | Duplicate a page | Provider-documented write; keep disabled until controlled verification |
| notion-create-database | Create a database | Provider-documented write; keep disabled until controlled verification |
| notion-create-folder | Create a folder | Provider-documented write; keep disabled until controlled verification |
| notion-update-data-source | Update a data source | Provider-documented write; keep disabled until controlled verification |
| notion-create-view | Create a view | Provider-documented write; keep disabled until controlled verification |
| notion-update-view | Update a view | Provider-documented write; keep disabled until controlled verification |
| notion-query-data-sources | Query data sources | Provider-documented; live Finta discovery pending |
| notion-query-meeting-notes | Query meeting notes | Provider-documented; live Finta discovery pending |
| notion-create-comment | Create a comment | Provider-documented write; suitable only for a controlled reversible test |
| notion-get-comments | Retrieve comments | Provider-documented; live Finta discovery pending |
| notion-get-teams | Retrieve teams | Provider-documented; live Finta discovery pending |
| notion-get-users | Retrieve users | Provider-documented; live Finta discovery pending |
| notion-get-async-task | Check asynchronous task status | Provider-documented; live Finta discovery pending |
Setup and proof path
- Update the Finta catalog endpoint from https://mcp.notion.com/sse to https://mcp.notion.com/mcp.
- Change the connector transport from legacy SSE to Streamable HTTP and verify OAuth metadata against the preferred endpoint.
- Confirm that Finta's callback base is the intended production domain before starting OAuth.
- In Finta, open Aurora, select the plus control, choose Connect App, and select Notion.
- Complete Notion's interactive OAuth as the intended workspace user.
- Review the pages, data sources, teams, and workspace content that user can already access in Notion.
- Capture the exact tools/list response rather than assuming every provider-documented tool is enabled.
- Use notion-fetch to confirm the workspace context and current_tool_access.
- Read one known non-sensitive fundraising page and reconcile its ID, URL, title, and last-edited time in Notion.
- Keep all write tools disabled during initial read verification.
- If writes are later tested, create and delete a controlled comment or make another reversible change in a dedicated test page.
- Test file upload separately with an approved non-sensitive file below the documented limit, capture the attachment result, and remove the test artifact.
Flagship workflow
Fundraising knowledge to source-backed investor update
This workflow turns scattered workspace knowledge into a claim ledger before it becomes investor communication. Stale numbers, conflicting sources, and missing ownership stay visible instead of being smoothed over by a generated summary.
- Confirm the connected Notion user, workspace, and current tool access.
- Search approved fundraising pages and data sources for traction, milestones, risks, pipeline, use of funds, and investor commitments.
- Fetch the original pages and retain page IDs, URLs, titles, and last-edited timestamps.
- Build a claim-to-source ledger for every material statement intended for the investor communication.
- Flag conflicting numbers, stale pages, unsupported claims, unclear ownership, and missing evidence.
- Ask the user to resolve conflicts before treating one value as authoritative.
- Combine approved Notion evidence with Finta relationship context for the intended investor or fund audience.
- Draft an investor update or meeting memo that cites the underlying source pages.
- Show any proposed Notion page, comment, database, or attachment change before execution.
- Stop until the user approves the exact target, content, permissions, and rollback path.
Sample prompts
Search my approved Notion fundraising pages for the latest traction, milestones, risks, and use of funds. Return every source and last-edited time. Draft an investor update, but do not write it back.Find conflicting fundraising target, round size, or runway values across authorized Notion pages. Cite each page, show its last-edited time, and ask me which source is authoritative.If notion-create-file-upload appears in the connected tool list, prepare to upload this approved twelve MiB board PDF and attach it to the selected page. Show the destination and complete change set before doing anything.
Expected output
The output specification below describes the evidence a useful result should contain. It is not presented as a live tool receipt unless the verification ladder says otherwise.
| Output field | Expected evidence |
|---|---|
| Connected context | Notion workspace, user, and current_tool_access |
| Source inventory | Page or data-source ID, URL, title, owner when available, and last-edited timestamp |
| Claim ledger | Each material claim paired with its exact source |
| Conflict or staleness | Competing values, old sources, unsupported statements, and required user decision |
| Finta relationship context | Audience, relevant prior concern, relationship owner, timing, and commitment context |
| Draft communication | Source-backed investor memo or update |
| Proposed Notion write | Target, operation, content, attachment, before state, and rollback plan |
| Approval state | Prepared but not executed |
| Completed writes | None in an illustrative output or read-only run |
| Limitations | Permission, Notion AI, plan, rate, tool-access, file-size, or source-age caveat |
Permissions and limitations
- Notion MCP access follows the authorizing user's existing Notion permissions.
- The hosted connection requires interactive user OAuth rather than a general headless bearer-token flow.
- Tool availability varies by plan and is reported through current_tool_access.
- Search across eligible connected sources can require the applicable Notion AI functionality; otherwise search remains limited to authorized Notion workspace content.
- Notion documents per-user and workspace-level rate limits, with lower limits for some search or tool operations.
- The current standard guidance averages roughly one hundred eighty requests per minute per user, but the live server and account limits remain authoritative.
- notion-create-file-upload currently documents a single-part local-file flow up to twenty MiB. Workspace and plan limits still apply.
- notion-download-attachment is limited to supported UTF-8 text content and is not a general promise to download arbitrary binary files.
- Provider-documented write tools must remain disabled until a controlled reversible test and rollback are complete.
- A source-backed draft must preserve page URLs and last-edited timestamps so stale evidence is visible.
- The legacy SSE endpoint remains a fallback, but the Finta catalog should move to the preferred Streamable HTTP endpoint before claiming current alignment.
Verification ladder
| Evidence level | Evidence | State |
|---|---|---|
| Level 0 | Notion MCP overview, setup, tools, file, and security documentation reviewed | Complete, August 22, 2026 |
| Level 1 | Finta Notion endpoint, transport, metadata URL, and auth mode inspected | Complete, August 22, 2026; endpoint remediation required |
| Level 2 | Catalog moved to https://mcp.notion.com/mcp with Streamable HTTP | Pending |
| Level 3 | Authenticated Notion OAuth receipt | Pending |
| Level 4 | Workspace and current_tool_access confirmed with notion-fetch | Pending |
| Level 5 | Exact tools/list names and descriptions captured | Pending |
| Level 6 | One known fundraising page returned and reconciled | Pending |
| Level 7 | One source-backed claim ledger manually checked | Pending |
| Level 8 | One reversible comment or page change completed and rolled back | Pending |
| Level 9 | Controlled file upload, attachment, and cleanup verified if claimed | Pending |
| Level 10 | Public page, corrected upload copy, metadata, image, and responsive rendering | Complete, August 22, 2026 |