Sinapsi
ItalianoSign in

Developers

One credential model, two protocols: MCP for assistants, REST for your code. Same tokens everywhere.

MCP endpoints

Every endpoint speaks Streamable HTTP (MCP). Works with Claude (Code, Desktop, claude.ai), the Claude API's MCP connector, and any MCP client.

  • https://sinapsi.wiki/mcp/hub/ — all public wikis, no auth: call list_wikis, then pass the id as the wiki parameter of search/get_page/neighbors. Switching wiki is a parameter, not a state.
  • https://sinapsi.wiki/mcp/w/<id>/ — one public wiki, isolated by URL, no auth.
  • https://sinapsi.wiki/mcp/ — your private spaces: Bearer token (account or space token, generated in-app), or sign in via OAuth from Claude Desktop / claude.ai. With an account credential, use my_spaces and the space parameter to move between your spaces.

REST API

The same account token works on /api/v1 (space tokens are MCP-only). Generate one in the app: Spaces → “Build a wiki with your assistant” → Generate command.

# your spaces
curl -H "Authorization: Bearer $SINAPSI_TOKEN" https://sinapsi.wiki/api/v1/spaces

# ask a space, with citations and frontier notes
curl -H "Authorization: Bearer $SINAPSI_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"question": "what tone of voice does the brand use?"}' \
  https://sinapsi.wiki/api/v1/spaces/<space-id>/ask

Machine-readable schema: OpenAPI (JSON). Public wikis need no token: GET /api/v1/public/wikis and friends.

Use it from an agent

With the Claude API, point the MCP connector at us — your agent gets search, get_page, neighbors, confirm_use as tools:

client.beta.messages.create(
    model="claude-opus-4-8", max_tokens=2048,
    betas=["mcp-client-2025-11-20"],
    mcp_servers=[{"type": "url", "name": "sinapsi",
                  "url": "https://sinapsi.wiki/mcp/",
                  "authorization_token": SINAPSI_TOKEN}],
    tools=[{"type": "mcp_toolset", "mcp_server_name": "sinapsi"}],
    messages=[{"role": "user", "content": "…"}],
)

Connect from any client

Claude Code — the in-app command works as-is; it applies to the current project folder (scope local). Add -s user to make it available in every project. If you skip the header, run /mcp to sign in with OAuth.

Claude Desktop / claude.ai — Settings → Connectors → add https://sinapsi.wiki/mcp/ and sign in. Available on every plan (Free includes one custom connector). The connection runs from Anthropic's cloud, so it works the same on web, desktop and mobile.

ChatGPT (Plus/Pro/Business) — Settings → Apps & Connectors → enable Developer mode → Create app → https://sinapsi.wiki/mcp/. ChatGPT connectors sign in with OAuth (we support it out of the box) — static Bearer tokens are not an option in the UI.

OpenAI Responses API — pass the token on every call:

tools=[{"type": "mcp", "server_label": "sinapsi",
        "server_url": "https://sinapsi.wiki/mcp/",
        "authorization": SINAPSI_TOKEN, "require_approval": "never"}]

VS Code / GitHub Copilot — .vscode/mcp.json (note the key is servers):

{"servers": {"sinapsi": {"type": "http",
  "url": "https://sinapsi.wiki/mcp/",
  "headers": {"Authorization": "Bearer YOUR_TOKEN"}}}}

Gemini CLI — gemini mcp add --transport http sinapsi https://sinapsi.wiki/mcp/ --header "Authorization: Bearer YOUR_TOKEN" (in settings.json the key is httpUrl, not url).

Cursor / Windsurf / Cline — same endpoint and header; the transport key differs per client: url (Cursor), serverUrl (Windsurf), "type": "streamableHttp" (Cline).

Fair use

Requests are rate-limited per token/IP (HTTP 429 with Retry-After when exceeded — generous for interactive and agentic use). Tokens are credentials: treat them like passwords, revoke them in-app if exposed. For high-volume commercial use of the public corpus, write to privacy@sinapsi.wiki.