
Connects your AI assistant to Aiqbee's knowledge graph platform for architecture and portfolio management. You get 25 tools covering brain management, neuron CRUD operations, relationship mapping, and access control. The server handles OAuth automatically, so no API keys to manage. It supports both streamable HTTP and stdio transports, making it work with Claude Desktop, Cursor, VS Code, and other MCP clients. Use it when you need to search across architecture decisions, create and link knowledge nodes, or manage team access to your digital strategy documentation without leaving your AI chat. Everything runs through their hosted MCP endpoint at mcp.aiqbee.com.
Connect AI assistants to your Aiqbee brains via the Model Context Protocol.
Search, create, and link knowledge across your architecture, portfolio, and digital strategy - all through natural conversation with your AI assistant.
Aiqbee is a remote MCP server (Streamable HTTP) at https://mcp.aiqbee.com/mcp with OAuth 2.0 sign-in.
| AI Tool | Integration | Setup |
|---|---|---|
| Claude Code | Plugin or CLI | See below |
| Claude Desktop / claude.ai | Custom Connector | See below |
| ChatGPT | Custom MCP plugin | See below |
| Cursor | MCP Config / Deep link | See below |
| VS Code / GitHub Copilot | .vscode/mcp.json | See below |
| Gemini CLI | Extension | See below |
| OpenAI Codex CLI | config.toml | See below |
| Windsurf | MCP Config | See below |
| Zed | Context server | See below |
| Grok (xAI API) | Remote MCP tool | See below |
| Any stdio client | npx | npx -y @aiqbee/mcp |
Plugin (includes the /brain skill), from your shell:
claude plugin marketplace add AIQBee/aiqbee-ai
claude plugin install aiqbee@aiqbee-marketplace
Inside a Claude Code session, use /plugin marketplace add AIQBee/aiqbee-ai then /plugin install aiqbee@aiqbee-marketplace.
Or add the server directly:
claude mcp add --transport http aiqbee https://mcp.aiqbee.com/mcp
Then run /mcp inside Claude Code (or claude mcp login aiqbee from your shell) to sign in.
Claude Desktop and claude.ai connect to remote servers through custom connectors, not claude_desktop_config.json:
Aiqbee, remote MCP server URL: https://mcp.aiqbee.com/mcp. Click Continue.On Team and Enterprise plans, an Owner adds the connector under Organization settings → Connectors first; members then connect individually. Connectors added here are also available in Claude Code when signed in with the same Claude account.
Alternatively, use the npx bridge in claude_desktop_config.json.
ChatGPT (web) adds custom MCP servers as plugins:
Aiqbee; under Connection enter https://mcp.aiqbee.com/mcp; authentication: OAuth.Availability depends on your plan and workspace policies. The ChatGPT desktop app shares MCP configuration with Codex; see OpenAI Codex CLI.
One-click install link (open in a browser): Add to Cursor
Or add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"aiqbee": {
"url": "https://mcp.aiqbee.com/mcp"
}
}
}
Run MCP: Add Server from the Command Palette and choose HTTP, or add to .mcp.json at your workspace root (or ~/.copilot/mcp-config.json for all workspaces):
{
"mcpServers": {
"aiqbee": {
"type": "http",
"url": "https://mcp.aiqbee.com/mcp"
}
}
}
The VS Code–specific .vscode/mcp.json format (top-level servers instead of mcpServers) also works.
Use the tools from Copilot Chat in Agent mode.
gemini extensions install https://github.com/AIQBee/aiqbee-ai
Restart Gemini CLI and run /mcp auth aiqbee if not prompted.
Or add the server directly:
gemini mcp add --transport http aiqbee https://mcp.aiqbee.com/mcp
codex mcp add aiqbee --url https://mcp.aiqbee.com/mcp
Or add to ~/.codex/config.toml (shared by Codex CLI, the Codex IDE extension and the ChatGPT desktop app):
[mcp_servers.aiqbee]
url = "https://mcp.aiqbee.com/mcp"
Then sign in:
codex mcp login aiqbee
For the Cascade agent, open … → Open MCP config file in the Cascade panel (~/.config/devin/mcp_config.json on macOS/Linux, %APPDATA%\devin\mcp_config.json on Windows; older Windsurf versions used ~/.codeium/windsurf/mcp_config.json) and add:
{
"mcpServers": {
"aiqbee": {
"serverUrl": "https://mcp.aiqbee.com/mcp"
}
}
}
In Zed, open Settings → AI → MCP Servers → Add Server → Add Remote Server, or add to settings.json (Zed prompts for OAuth sign-in):
{
"context_servers": {
"aiqbee": {
"url": "https://mcp.aiqbee.com/mcp"
}
}
}
The xAI API supports remote MCP servers as a tool (Responses API / xAI SDK). xAI connects to the server on your behalf, so it cannot run the interactive OAuth flow; pass an Aiqbee OAuth access token in authorization:
{
"model": "<grok-model>",
"input": "List all my Aiqbee brains",
"tools": [
{
"type": "mcp",
"server_url": "https://mcp.aiqbee.com/mcp",
"server_label": "aiqbee",
"server_description": "Aiqbee knowledge graph (brains, neurons, relationships)",
"authorization": "<AIQBEE_ACCESS_TOKEN>"
}
]
}
Use allowed_tools (allowed_tool_names in the xAI SDK) to limit Grok to read-only tools such as aiqbee_search and aiqbee_fetch. See xAI Remote MCP Tools.
For MCP clients that only support stdio transport:
{
"mcpServers": {
"aiqbee": {
"command": "npx",
"args": ["-y", "@aiqbee/mcp"]
}
}
}
Point any MCP client that supports Streamable HTTP and OAuth at:
https://mcp.aiqbee.com/mcp
Aiqbee uses OAuth 2.0 with secure authorization. When you first connect, your MCP client will prompt you to sign in. The server supports:
No API keys needed - just sign in with your existing Aiqbee account.
| Tool | Description | Permission |
|---|---|---|
aiqbee_list_brains | List all brains you have access to | Read |
aiqbee_get_brain_info | Get brain metadata and statistics | Read |
aiqbee_edit_is_allowed | Check if MCP editing is enabled for a brain | Read |
aiqbee_list_brain_templates | List available brain templates for brain creation | Read |
aiqbee_create_brain | Create a new brain (optionally from a template) | — |
aiqbee_update_brain | Update brain name, description, or settings | Owner |
aiqbee_delete_brain | Delete a brain permanently | Owner |
| Tool | Description | Permission |
|---|---|---|
aiqbee_search | Search neurons in your knowledge graph | Read |
aiqbee_fetch | Get full neuron content and metadata | Read |
aiqbee_list_neurons | Paginated neuron listing with filtering | Read |
| Tool | Description | Permission |
|---|---|---|
aiqbee_list_neuron_types | List all neuron types in a brain | Read |
aiqbee_add_neuron_type | Create a new neuron type | Owner |
aiqbee_edit_neuron_type | Update a neuron type's properties | Owner |
aiqbee_delete_neuron_type | Delete a neuron type (with optional neuron reassignment) | Owner |
| Tool | Description | Permission |
|---|---|---|
aiqbee_create_neuron | Create a new neuron in your brain | ReadWrite |
aiqbee_update_neuron | Update an existing neuron | ReadWrite |
aiqbee_delete_neuron | Delete a neuron | ReadWrite |
| Tool | Description | Permission |
|---|---|---|
aiqbee_get_relationships | Get incoming/outgoing relationships for a neuron | Read |
aiqbee_create_relationship | Create a link between two neurons | ReadWrite |
aiqbee_update_relationship | Update an existing relationship | ReadWrite |
aiqbee_delete_relationship | Remove a relationship | ReadWrite |
| Tool | Description | Permission |
|---|---|---|
aiqbee_list_users | List users with access to a brain | Read |
aiqbee_grant_access | Grant a user access to a brain | Owner |
aiqbee_revoke_access | Revoke a user's access to a brain | Owner |
aiqbee_batch_update_access | Replace all access permissions in one operation | Owner |
Once connected, try asking your AI assistant:
Aiqbee is a web-based architecture, portfolio, and digital strategy management platform.
MIT License - see LICENSE for details.