KnowMapped
Try KnowMapped
AvailableProfessional

Model Context Protocol

Let your AI client work with the map.

Professional users can connect a compatible AI client to your KnowMapped account. It can use purpose-built tools to find, create, and refine maps.

Connect a clientView Professional

Agent-ready mapping

Collaborate without flattening the map into a prompt.

MCP gives an AI client a structured interface to KnowMapped. The client works with concepts, relationships, metadata, and layouts as map objects rather than treating the graph as an unstructured block of text.

01

Find and retrieve

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

02

Create and extend

Create maps, append findings, and use KnowMapped’s existing generation and credit controls.

03

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.

  1. 01

    Start at the resource server

    Configure a remote Streamable HTTP server with https://mcp.knowmapped.com/mcp. The initial unauthenticated request is expected to return 401 and a WWW-Authenticate challenge.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

Turn on Developer mode under Settings → Security and login. In the composer, open ChatGPT Plugins, use the plus button to create a developer-mode app, select Streamable HTTP, and enter https://mcp.knowmapped.com/mcp. Complete the browser authorization, then refresh the app’s tools before starting a new chat.

Read OpenAI’s developer-mode 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

KnowMapped remains authoritative.

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.

Each new map created through MCP uses 1 generation credit. Free and Professional users can use generation credits for MCP map creation. Reading or editing an existing map does not use credits. The creation preflight returns the current cost before a map is created, and failed validation does not consume credits.

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.

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
ScopePurpose
maps:readSearch and retrieve maps available to the connected account.
maps:createRun creation preflight and create maps.
maps:writeValidate and apply edits to maps where the account has edit access.

Current tools

search_knowmapped_maps

Search the connected account’s authorized map library.

get_knowmapped_map

Retrieve a full, compact, or summary map representation.

preflight_knowmapped_map_creation

Check eligibility and required credits before constructing a map.

create_knowmapped_map

Validate or create a map through KnowMapped’s shared creation service.

update_knowmapped_map

Validate or atomically apply revision-safe graph operations.

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 connected KnowMapped account has Professional access and is an owner or editor of that map.