AvailableProfessional

Model Context Protocol

Connect an AI client to KnowMapped.

With Professional, connect a compatible AI client to your KnowMapped account. Ask it to find a map, create one, edit concepts and relationships, or publish a completed public snapshot.

Connect a client View Professional

Remote MCP server

https://mcp.knowmapped.com/mcp

Streamable HTTP · OAuth 2.0 · PKCE

Map tools

Find, create, edit, and publish maps through conversation.

Through MCP, an AI client can read and change individual concepts, connections, map details, and layouts. It uses the permissions of your connected KnowMapped account.

Find and retrieve

Search the maps available to your account and request full, compact, or summary representations.

Create and extend

Prepare a map, review the one-credit charge, and confirm creation. Append findings to existing maps.

Publish and update

Make maps public or private, publish completed edits as public snapshots, and check delivery status.

Edit and arrange

Add, revise, connect, remove, and lay out map content with validation before changes are applied.

Connection guide

Register the endpoint, complete OAuth, load the tools.

Use a client that implements MCP Streamable HTTP and OAuth 2.0. Start with the MCP endpoint and let the client follow the protected-resource challenge to discover the authorization server. Do not hard-code authorization URLs or place KnowMapped credentials in client settings.

01
Configure the resource server
Configure a remote Streamable HTTP server with https://mcp.knowmapped.com/mcp. Authenticated operations use a 401 response and WWW-Authenticate challenge when authorization is required. Tool discovery may be available before sign-in.
02
Resolve OAuth metadata
Follow the challenge to the protected-resource metadata, resolve its authorization server, and read the authorization-server metadata. This is where the client learns the endpoints, scopes, PKCE method, and registration options.
03
Register a public client
Use a Client ID Metadata Document when supported; use Dynamic Client Registration as the compatibility fallback. The client must use token_endpoint_auth_method=none, and its redirect URI must be registered exactly.
04
Authorize with PKCE
Generate a PKCE S256 verifier and challenge, open the browser authorization request, then sign in and approve the requested map scopes. Credentials stay in the KnowMapped browser flow.
05
Initialize and load tools
Exchange the authorization code with the verifier and resource binding, send the bearer token to https://mcp.knowmapped.com/mcp, then run MCP initialization and tools/list. Refresh the client’s tools or start a new conversation after connecting.

OpenAI clients

Use KnowMapped with ChatGPT or Codex.

ChatGPT

Add a custom app.

Open ChatGPT Plugins, select the plus button, then Add custom MCP server. Enter https://mcp.knowmapped.com/mcp and choose OAuth authentication. Complete KnowMapped’s browser consent flow, install the resulting plugin, and invoke it in a new chat. Refresh its tools after a server update.

Read OpenAI’s MCP plugin guide

Codex

Add a remote MCP server.

Register the Streamable HTTP endpoint, then run the separate login command so Codex can complete the browser-based OAuth flow and cache the resulting credentials.

codex mcp add knowmapped --url https://mcp.knowmapped.com/mcp
codex mcp login knowmapped
codex mcp list

Read OpenAI’s Codex MCP guide

Access and billing

Your account permissions still apply.

Every request is limited by the connected account’s existing map access. A public link does not grant edit permission, and a client cannot bypass ownership or sharing controls.

MCP map creation requires Professional or an active Professional trial. Each successfully created map uses 1 generation credit. Preflight shows the cost and remaining balance; the client must ask you to confirm before charging. Failed validation uses no credits. Reading, editing, checking publication status, and publishing existing maps do not use creation credits.

Editing and publishing have separate permissions. Approve maps:write for content edits and maps:publish for public snapshots and visibility changes. Existing connections must request fresh consent to gain publishing access.

Connections have no scheduled refresh-credential expiry in the standard deployment. Clients renew short-lived access tokens automatically and must save each rotated refresh credential. Revocation, password changes, account restrictions, or lost refresh credentials can still require reconnecting.

Disconnect the integration from your client to remove its local connection. You can also revoke OAuth access from KnowMapped when you need to invalidate an existing authorization.

Public snapshots

Publish when the edits are ready.

Ask the agent to finish editing, then publish. Ordinary edits leave the existing public snapshot unchanged. First publication uses set_knowmapped_map_visibility and requires your explicit permission and confirmation that you have the right to publish.

For an already-public map, publish_knowmapped_map replaces the public snapshot with the completed draft. KnowMapped generates its public preview and applies the same moderation, restrictions, locks, and permissions as browser publishing.

Both actions need the current expected_revision and a unique idempotency_key of 1–200 characters. After a timeout, retry with the same key and identical arguments. A changed request needs a new key. Committed results can be recovered for 30 days without repeating publication or undoing later visibility changes.

Use get_knowmapped_publication_status to check the published revision, moderation, and delivery. A saved snapshot may still be awaiting delivery, and a pending review is not a successful publication. Revision differences mean content may have changed; operational changes also advance revisions.

To remove public access, ask the agent to make the map private. This removes the public snapshot, disables live viewing, and queues deletion of the public page and preview. Previously downloaded copies remain outside KnowMapped’s control.

Technical reference

Discovery, authorization, and tools.

The server follows MCP Streamable HTTP and OAuth discovery conventions. Clients should begin with the MCP endpoint rather than configuring authorization endpoints manually.

Discovery

MCP endpoint: https://mcp.knowmapped.com/mcp
Protected resource: https://mcp.knowmapped.com/.well-known/oauth-protected-resource/mcp
Authorization server: https://app.knowmapped.com

OAuth

Grant: Authorization code with PKCE S256
Client registration: Client ID Metadata Documents, with Dynamic Client Registration fallback
Resource: https://mcp.knowmapped.com/mcp

OAuth scopes used by KnowMapped MCP tools
Scope	Purpose
`maps:read`	Search and retrieve maps available to the connected account.
`maps:create`	Preflight, confirm, create, and recover map creation results.
`maps:write`	Validate and apply edits to maps where the account has edit access.
`maps:publish`	Make editable maps public or private, publish public snapshots, and check publication status. Does not grant content editing.

Read resource://knowmapped/capabilities for limits, creation costs, and the current tool contract. Retrieval supports independent node_offset and edge_offset values, with page_size up to 200. Summary requests load counts without graph content; paginated requests load only the requested rows. Compare revisions between pages and restart if they change.

Current tools

search_knowmapped_maps

Search the authorized map library.

get_knowmapped_map

Retrieve full or compact pages, or graph-free summary counts.

get_knowmapped_map_adjacency

Inspect a concept’s neighborhood by ID or exact unique label.

get_knowmapped_layout_summary

Inspect layout bounds and overlap statistics.

preflight_knowmapped_map_creation

Check eligibility, credits, and a retained graph draft.

create_knowmapped_map

Validate or prepare creation; credit use requires explicit confirmation.

confirm_knowmapped_map_creation

Confirm a retained draft and settle its one-credit creation charge.

get_knowmapped_map_creation_result

Recover a creation result after a dropped response.

get_knowmapped_update_schema

Get the authoritative operation schema before constructing edits.

update_knowmapped_map

Validate or apply one atomic, revision-safe graph patch.

set_knowmapped_map_visibility

Make a map public or private; first publication creates a snapshot.

publish_knowmapped_map

Publish or republish completed edits to an already-public map.

get_knowmapped_publication_status

Check snapshot revision, moderation, and delivery without downloading the graph.

Troubleshooting

Start with the client’s tool refresh.

Tools do not appear

Refresh the integration’s tools and begin a new conversation. An existing conversation may retain the tool list it received when it started.

Sign-in does not open

Disconnect and reconnect KnowMapped in the client. Confirm that the client supports OAuth for remote MCP servers.

A map cannot be changed

Confirm that the connection has maps:write and that your account can edit the map. Retrieve its current revision and check whether it is locked.

Publishing is unavailable

Request maps:publish and approve fresh consent. Refresh tool discovery. Your account still needs edit access; moderation or publishing restrictions may prevent publication.

A publication response was lost

Retry the identical request with its original key, then check publication status. Use a new key only for a new request.

A connection needs sign-in again

Check whether access was revoked or the client lost a rotated refresh credential. Refresh credentials have no scheduled expiry in the standard deployment, but clients must renew and save them correctly.