Skip to content
Noosphere
MCP server

Ask your graph questions
from the tools you use.

Noosphere speaks the Model Context Protocol. Point an MCP-aware client — Claude Code, Claude Desktop, Cursor, or anything else that implements the standard — at your account, and it can search entities, trace connections, and cite the source documents behind every answer, all in ordinary language.

Read-only by design

The server exposes retrieval tools and nothing else. There is no tool that can create, alter, or delete an entity, a relationship, or a document. An AI client connected to Noosphere can read the graph and reason about it; it cannot change what is in it.

Access uses the same API token that authorizes the browser extension. You can view or regenerate that token from your account once signed in; regenerating it immediately invalidates the old one.

Connecting a client

The endpoint is https://getnoosphere.com/mcp, spoken as JSON-RPC 2.0 over Streamable HTTP, authorized with a bearer token.

Claude Code

claude mcp add --transport http noosphere \
  https://getnoosphere.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN_HERE"

Claude Desktop, or any stdio-only client

{
  "mcpServers": {
    "noosphere": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://getnoosphere.com/mcp",
        "--header", "Authorization: Bearer YOUR_TOKEN_HERE"
      ]
    }
  }
}

Sign in to get your API token, then substitute it for YOUR_TOKEN_HERE.

Available tools

Tool What it does
search_entities Substring name search across the graph. Returns candidates with their identifiers, types, and connection counts — the usual starting point.
get_entity Look up a single entity by identifier or exact name. Refuses to guess when a name is ambiguous, and lists the candidates instead.
list_entity_relationships Every connection recorded for an entity, each with its plain-language description.
get_relationship The full set of source descriptions behind one relationship.
find_path Shortest path between two entities, up to six hops.
find_common_connections Entities directly connected to both of two given entities.
get_entity_sources The source documents that mention an entity, and what each one contributed.
graph_stats Totals for the graph plus its most-connected entities.

Questions it answers well

  • “Search Noosphere for entities named Ada Lovelace and tell me what types they are.”
  • “What is the shortest connection between these two organizations, and which documents establish each hop?”
  • “Who do these two people both know? Cite the sources.”
  • “What did the graph learn about this person, and from which uploads?”

Two people with the same name are two different nodes. Start with search_entities to find the right one, then pass its identifier to the other tools.