Blueprint Nexus Logo
Nexus
Developer Integrations & Model Context Protocol (MCP)
Platform/Documentation/Developer Integrations & Model Context Protocol (MCP)
Integrations & Connectors

Developer Integrations & Model Context Protocol (MCP)

Integrate Blueprint Nexus with your existing developer stack (GitHub, Linear, Google Calendar) and connect remote AI agents, Cursor IDE, Windsurf, Claude Desktop, and ChatGPT directly to your workspace Knowledge Graph via the official Remote MCP Server URLs.

Developer and SaaS Integrations Management
Connect GitHub, Linear, Google Calendar, and Composio for real-time bidirectional data flow.Live Interface

1. Connecting SaaS Developer Tools

  1. 1Click the Settings gear in the sidebar or open the Settings Modal > Integrations tab.
  2. 2Select the tool you want to connect (GitHub, Linear, Google Calendar, Composio).
  3. 3Click 'Connect' and authorize access via OAuth or paste your API token.
  4. 4Configure sync preferences (e.g. importing Linear issues as tasks, linking GitHub pull requests to graph nodes).

2. Custom AI Connectors & Remote MCP Server URLs

  1. 1Open Settings Modal > Integrations tab and locate the MCP Developer Suite.
  2. 2Copy your Remote MCP Server URL: `https://blueprintsociety.com/api/mcp/sse` for realtime SSE streaming, or `https://blueprintsociety.com/api/mcp/messages` for standard JSON-RPC HTTP.
  3. 3Generate a Workspace API Key (`bsc_live_...`) with your desired permissions (`bkn:read`, `bkn:write`, `bkn:ingest`, `mcp:tools`).
  4. 4For Cursor IDE / Windsurf: Add the `remote_mcp_server_url` (SSE) into your `.cursor/mcp.json` with your API key.
  5. 5For Claude Desktop / CLI Agents: Use the `remote_mcp_messages_url` in `claude_desktop_config.json` via `@blueprint-nexus/mcp-server`.
  6. 6For ChatGPT Custom GPTs: Import the OpenAPI 3.1 specification URL into the GPT Action Editor with Bearer authentication.
  7. 7Test the live connection and tool executions using the built-in interactive MCP Test Console.

Remote MCP Server Endpoints & Connectors

Standard protocols and remote URL endpoints

Remote SSE URLhttps://blueprintsociety.com/api/mcp/sse (Real-time SSE for Cursor/Windsurf)
Remote Messages URLhttps://blueprintsociety.com/api/mcp/messages (JSON-RPC 2.0 tool execution)
OpenAPI Spec URLhttps://blueprintsociety.com/api/mcp/openapi?workspace_id=... (ChatGPT Actions)
Supported IDEsCursor IDE, Claude Desktop, Windsurf, Continue, Zed, VS Code
Supported SaaSGitHub, Linear, Google Calendar, Composio (100+ integrations)

Integration Code & Config Snippets

{
  "mcpServers": {
    "blueprint": {
      "type": "sse",
      "url": "https://blueprintsociety.com/api/mcp/sse?api_key=bsc_live_YOUR_KEY"
    }
  }
}

Pro Tips & Best Practices

•Use the Remote SSE URL (`/api/mcp/sse`) for IDE copilots (Cursor, Windsurf) to stream real-time workspace updates.
•Use the Remote Messages URL (`/api/mcp/messages`) for backend autonomous agent fleets, LangChain/LlamaIndex, and CI/CD pipelines.
•Scope Workspace API keys appropriately (e.g. read-only `bkn:read` for query-only external assistants, `bkn:write` for builders).