Skip to main content
Topicflow runs a hosted Model Context Protocol server that lets AI assistants like Claude, Cursor, ChatGPT, and any other MCP-compatible client read your Topicflow workspace and draft updates on your behalf — with explicit confirmation before anything is written.

Server URL

The endpoint speaks streamable HTTP MCP and is protected by OAuth 2.1 with PKCE. The first time your client connects you will be redirected to Topicflow to sign in and approve access. No API keys or static tokens to manage.

Connecting a client

Most MCP clients accept a JSON config block. Paste this into your client’s MCP server settings:

Claude Desktop and Claude Code

Add the server in Settings → Connectors → Add custom connector (Claude Desktop) or run claude mcp add --transport http topicflow https://app.topicflow.com/mcp (Claude Code). Claude will open a browser window for the Topicflow sign-in.

Cursor

Settings → MCP → Add new MCP server, then paste the JSON config above. Cursor handles the OAuth flow automatically.

ChatGPT

In a ChatGPT workspace that supports custom connectors, add a new connector with the URL above and choose OAuth as the auth method. ChatGPT will discover the Topicflow authorization server and prompt you to sign in.

Other clients

Any client that supports MCP over streamable HTTP with OAuth 2.1 dynamic client registration will work. Point it at the URL above — discovery and registration happen automatically.

OAuth scopes

When you approve a connection, the client requests one or more of these scopes. Each area of Topicflow has its own read and write scope, so a client can be given access to your goals without also being given your private notes. Access is bound to you and your organization. The MCP server only ever returns data you can already see in Topicflow — visibility rules for private feedback, other people’s one-on-ones, and team-scoped goals are enforced exactly as they are in the app.

Available tools

Read tools

Reviews have their own set of read tools:

Write tools

Write tools never commit on the first call. They follow a preview → confirm pattern so the assistant can show you exactly what will be created or changed before anything lands in Topicflow. create_private_note is the one exception to the preview pattern — it saves straight away, because a private note is only ever visible to the person who wrote it. Reviews follow the same pattern: Roles and competencies have their own set, used by admins to build a role framework in conversation — optionally starting from a document you already have: A typical write flow:
  1. Assistant gathers context with read tools (list_meetings, query_external_events, list_assessments).
  2. Assistant calls a write tool and shows you the preview it returns.
  3. You confirm.
  4. Assistant calls confirm_creation with the pending ID, and the record is created or updated in Topicflow.
If you don’t confirm, nothing is written.

Example prompts

Once connected, you can talk to your assistant the same way you would talk to Topicflow AI inside Topicflow:
  • “What did Riley ship this sprint? Draft recognition tied to our ‘ship fast’ core value.”
  • “Summarize my last three one-on-ones with Jordan and suggest topics for tomorrow.”
  • “Look at my open PRs and draft a goal check-in for my Q2 reliability goal.”
  • “What feedback have I given in the last month? Is anything missing for my upcoming review?”
  • “Update my Q3 reliability goal to reflect the progress from last week’s deploy.”
  • “Walk me through my self-review one question at a time, using my goals and shipped work as a starting point.”
  • “Which of my team hasn’t submitted their review yet, and were they actually sent the reminder?”
  • “Analyze the transcript from this morning’s stand-up and list the decisions we made.”

Privacy and limits

  • The MCP server respects every visibility rule in Topicflow. Private feedback stays private, and you cannot see other people’s one-on-ones or scoped goals through MCP that you couldn’t see in the app.
  • Write tools always require explicit confirmation through confirm_creation. An assistant cannot create or edit feedback, goals, check-ins, recognition, or review answers silently. The single exception is create_private_note, which writes immediately because the note is only ever visible to you.
  • Private notes are yours alone. list_private_notes returns only notes you wrote, and never anyone else’s.
  • You can revoke a connected client at any time from Settings → Integrations → Connected apps. Revoking immediately invalidates the OAuth tokens.
  • Tokens are short-lived and refreshed automatically by the client. There are no long-lived API keys to rotate.

What’s next

Topicflow AI

Use Topicflow’s built-in AI assistant

Integrations

Connect work tools that feed query_external_events

Roles and permissions

Understand what each user can see

Visibility and privacy

See how visibility rules are enforced