MCP Setup
Sibyl exposes an HTTP MCP endpoint at /mcp. Use a scoped API key with the mcp scope for client integrations.
Create The Key
sibyl auth api-key create --name "mcp-client" --scopes mcpUse a project or memory-space restriction when the client should only see a specific workspace:
sibyl auth api-key create --name "project-agent" \
--scopes mcp \
--projects proj_abc123Shared HTTP Configuration
Most MCP clients accept the same HTTP shape:
{
"mcpServers": {
"sibyl": {
"type": "http",
"url": "https://sibyl.example.com/mcp",
"headers": {
"Authorization": "Bearer sk_live_replace_me"
}
}
}
}Keep the key out of committed files. Prefer your client's secret store or a local ignored config file.
Cursor
Add Sibyl as an HTTP MCP server in Cursor's MCP settings:
{
"mcpServers": {
"sibyl": {
"type": "http",
"url": "https://sibyl.example.com/mcp",
"headers": {
"Authorization": "Bearer sk_live_replace_me"
}
}
}
}Restart the MCP server from Cursor's settings after editing the config.
Claude Code
Use Claude Code's MCP configuration with the same HTTP server entry:
{
"mcpServers": {
"sibyl": {
"type": "http",
"url": "https://sibyl.example.com/mcp",
"headers": {
"Authorization": "Bearer sk_live_replace_me"
}
}
}
}Add a short project instruction so agents actually use the memory loop:
Search Sibyl before non-trivial work, capture durable gotchas after solving them, and keep task
state current when work spans multiple steps.Claude Desktop
Claude Desktop can use the same HTTP MCP server entry in its MCP server config:
{
"mcpServers": {
"sibyl": {
"type": "http",
"url": "https://sibyl.example.com/mcp",
"headers": {
"Authorization": "Bearer sk_live_replace_me"
}
}
}
}Restart Claude Desktop after changing the MCP config.
Verify
Ask the client to search Sibyl for a known memory. If the request fails:
- Confirm the API key starts with
sk_live_orsk_test_. - Confirm the key has the
mcpscope. - Confirm the client can reach
https://sibyl.example.com/mcp. - Check Settings, Security, API Keys to make sure the key was not revoked.
