MCP integrations

Connect your agent to Knowen.

Give your assistant one endpoint to search, read, and update your project memory—so each session starts with the context the last one left.

MCP serverOne endpoint for every compatible client

https://mcp.knowen.org/mcp

Claude Desktop

Claude Desktop connects as a custom connector using OAuth. No API token is needed.

Open Settings → Connectors in Claude on the web or desktop. Custom connectors cannot be added from mobile; once connected, they should be available there.
Click Add custom connector (it may be under “Browse connectors” or an Add menu, depending on your plan).
Enter a name such as Knowen, then set the server URL shown above.
Save, click Connect, then sign in to Knowen and approve access.
Enable Knowen for a new chat from the tools or connectors menu.

Claude Code

Add the Knowen server with one command:

claude mcp add knowen https://mcp.knowen.org/mcp --transport http --scope user --header "Authorization: Bearer YOUR_KNOWEN_API_TOKEN"

Replace YOUR_KNOWEN_API_TOKEN with an API token from Knowen. Keep it private.

This setup uses a bearer API token.

Claude Code for VS Code

Add Knowen as a remote HTTP MCP server in the Claude Code extension.

Install and open the Claude Code extension from the VS Code Extensions panel.
Open the command menu with “/” and choose Customize → MCP servers.
Choose Add server, then enter these values:

Name	`Knowen`
Transport	HTTP (remote)
URL	`https://mcp.knowen.org/mcp`
Authorization header	`Authorization: Bearer YOUR_KNOWEN_API_TOKEN`
Scope	`user`

Start a new session and check that Knowen shows as Connected.

Get a token from Settings → API Tokens. Keep it private.

This setup uses a bearer API token.

Cursor

Cursor supports remote MCP servers in the editor and Cursor CLI. Add Knowen to your project’s .cursor/mcp.json or ~/.cursor/mcp.json:

{
  "mcpServers": {
    "knowen": {
      "url": "https://mcp.knowen.org/mcp"
    }
  }
}

Add an Authorization header with your API token if you prefer token authentication. You can also connect with OAuth when your client prompts you to sign in to Knowen.

Choose Knowen sign-in or a bearer API token.

ChatGPT

Connect Knowen as a remote MCP server using the URL shown above. Select the authentication method offered for the Knowen connection.

In ChatGPT, open Settings → Security and login and turn on Developer mode. Availability depends on your account and workspace policy.
Open ChatGPT Plugins, select the plus button, and enter a name and description for the connection.
Under Connection, enter the server URL shown above and choose the authentication method.
Create the connection and review the tools ChatGPT discovers.
Start a new conversation, add Knowen from the tools menu, and try a search in your knowledge graph.

OpenAI’s current connection guide has the latest setup steps. Confirm write actions when ChatGPT asks.

Follow the authorization prompt when connecting Knowen.

Other MCP clients

Any MCP client that supports Streamable HTTP can connect to Knowen.

Transport	Streamable HTTP
Endpoint URL	`https://mcp.knowen.org/mcp`
Authentication	`Authorization: Bearer YOUR_KNOWEN_API_TOKEN`

Refer to your client’s documentation for how to add a remote MCP server.

Create and manage tokens in Settings → API Tokens. Keep config containing tokens out of version control.

This setup uses a bearer API token.

What your agent can do

Create, read, update, and delete nodes
Manage edges and semantic connections
Search your trees and the public graph
Manage file attachments, Inbox, comments, and notifications
Check usage quotas

Keep tokens private

API tokens carry your account’s access. Keep them private, and revoke them from Settings → API Tokens if one is exposed.

Manage API tokens →

Next: tell it when to remember

Add a few lines to AGENTS.md so your agent reads from Knowen before it works and writes back what it decides and verifies.

Copy the AGENTS.md instructions →

Troubleshooting

If the connection doesn’t work.

“Authentication required”

Verify that you signed in to the correct account or that your API token has not been revoked. Create a new token from Settings → API Tokens if needed.

My client cannot see my private trees

Confirm that you connected using the account that owns those trees.

Connection refused or timeout

Ensure your network allows outbound HTTPS to mcp.knowen.org.

Tools are not appearing

Restart your MCP client and start a new session so it can discover the server tools.

Still stuck?

A place to pick up where you left off

Give your agent a project to remember.

Create a project, give it context, and connect the coding agents you already use.

Explore Knowen ↗Connect your agent →

Account creation is by invitation during beta. You can explore public knowledge as a guest.