← Back to documentation

Connect to Siftable hosted MCP

Use one remote endpoint to give an MCP-compatible client permission-scoped access to your Siftable projects, tasks, work queues, notes, datasets, calendar, and people.

Hosted quickstart

The hosted server uses Streamable HTTP and OAuth. Start with the URL alone:

https://siftable.io/api/v1/mcp

1. Add the URL as a remote MCP server or connector in your client.
2. Choose Connect, Authenticate, or Login when the client prompts you.
3. Complete the Siftable consent screen. Do not create or paste a PAT for this path.
4. Call context_current, then use find_capability to discover the right tool.

Do not use the retired /sse endpoint. Adding an Authorization header selects static-token mode and prevents OAuth scope elevation.

Client setup

ChatGPT

Confirm Developer Mode is available for your plan and enabled for your account. In Settings → Apps → Create (or Workspace settings → Apps → Create for admins), enter the hosted MCP URL, choose OAuth, select Scan Tools, complete Siftable consent, then select Create. Open a new chat, select the draft Siftable app from the tools menu, and run the verification calls below.

Codex

codex mcp add siftable --url "https://siftable.io/api/v1/mcp"

# The add command starts OAuth automatically. If you need to reconnect later:
codex mcp login siftable

Cursor

{
  "mcpServers": {
    "siftable": {
      "url": "https://siftable.io/api/v1/mcp"
    }
  }
}

Claude

Add a remote connector, enter the hosted MCP URL, and complete OAuth. A Claude remote connector is different from a local Claude Desktop stdio configuration.

Grok

The Siftable Grok plugin uses the same hosted MCP URL. Until the marketplace package is available, add that URL to a local plugin's .mcp.json and complete OAuth when Grok prompts you.

Verify the connection

Run these checks in order:

1. context_current should report the hosted transport and your authorization scopes.
2. project_list or task_list should return your records.
3. find_capability should explain whether a requested action is callable, needs approval, or is local-only.
4. A missing work scope should return recovery instructions or an approval link, not crash the connection.

Representative tools

Tool	Description
project_list	List all projects
project_get_context	Get full project context
task_list	List tasks
task_create	Create a new task
task_complete	Mark task complete
note_search	Search knowledge base
note_create	Create a note
calendar_list_events	List calendar events
people_search	Search contacts
find_capability	Discover callable and requestable capabilities
request_capability	Inspect authorization recovery or intentionally request an OAuth challenge
code_memory_search	Search curated code facts
code_memory_store	Store a durable code fact with provenance

Hosted and local boundaries

Siftable MCP does not read your filesystem or index repository source. Inspect source in an authorized local checkout with your editor, rg, or git grep. code_memory_search retrieves previously curated facts stored in Siftable; it is not codebase or source-code search.

When to use a PAT or local stdio

Use a PAT for non-interactive automation or a client that cannot perform OAuth. Use the published @siftable/mcp-server package when a client requires local stdio transport; it still does not search repository files. PAT scopes are fixed; replacing the credential is required when additional scopes are needed.

{
  "mcpServers": {
    "siftable-local": {
      "command": "npx",
      "args": ["@siftable/mcp-server"],
      "env": {
        "SIFT_API_URL": "https://siftable.io",
        "SIFT_PAT": "sift_pat_YOUR_TOKEN_HERE"
      }
    }
  }
}

← Back to documentation