aiqbee
Connect AI assistants to your Aiqbee brains via the Model Context Protocol.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Aiqbee List Brains: Lists all brains the authenticated user can access. Returns brain IDs, names, descriptions, access levels, and MCP URLs. Use this to discover available brains before calling other
- Aiqbee Get Brain Info: Returns brain metadata including name, description, whether it's personal, and if MCP editing is allowed.
- Aiqbee Edit Is Allowed: Checks if MCP editing (create, update, delete) is allowed for a brain. Checks both the user's permission level AND the brain's AllowMCPEditing setting.
What data it sees
Do you need an account
No: the server works without sign-in
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.
How to connect
How to connect aiqbee to Claude
The server address to paste into Claude settings:
https://aiqbee-ai--aiqbee.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect aiqbee to ChatGPT
The server address to paste into ChatGPT settings:
https://aiqbee-ai--aiqbee.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect aiqbee to Cursor
The server address to paste into Cursor settings:
https://aiqbee-ai--aiqbee.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (25)
Raw names from tools/list. Only developers need these.
| aiqbee_list_brains | Lists all brains the authenticated user can access. Returns brain IDs, names, descriptions, access levels, and MCP URLs. Use this to discover available brains before calling other tools. Only available on the brain-agnostic /mcp endpoint. |
| aiqbee_get_brain_info | Returns brain metadata including name, description, whether it's personal, and if MCP editing is allowed. |
| aiqbee_edit_is_allowed | Checks if MCP editing (create, update, delete) is allowed for a brain. Checks both the user's permission level AND the brain's AllowMCPEditing setting. |
| aiqbee_create_brain | Creates a new brain. The authenticated user becomes the owner. Personal brains are only visible to the owner; organization brains are visible to all tenant users. |
| aiqbee_update_brain | Updates a brain's settings. Only provided fields are changed. Requires Owner access. |
| aiqbee_delete_brain | Deletes a brain permanently. WARNING: This action cannot be undone. The brain and ALL its neurons, relationships, and access permissions will be permanently deleted. Requires Owner access. |
| aiqbee_list_brain_templates | Lists available brain templates that can be used when creating a new brain. Templates define pre-configured neuron types. Pass the template id as brain_template_id to aiqbee_create_brain. |
| aiqbee_search | Searches the brain's knowledge graph for neurons matching the query. Returns neuron ID, title, snippet, type, and URL for each match. When include_related is True (default), also includes neurons connected via synapses. |
| aiqbee_fetch | Retrieves complete neuron data including content and metadata. Use get_relationships to fetch synapse/relationship data separately. |
| aiqbee_list_neurons | Returns a paginated list of neurons, optionally filtered by type. Includes pagination information (total count, page number, page size, has more). |
| aiqbee_get_relationships | Returns all relationships (synapses) for a specific neuron, including incoming and outgoing connections. Each synapse includes the related neuron ID, name, type, and link description. |
| aiqbee_list_neuron_types | Returns a list of neuron types with their IDs, names, descriptions, and whether they represent files. |
| aiqbee_add_neuron_type | Creates a new neuron type in the brain. Requires Owner access and MCP editing to be enabled. |
| aiqbee_edit_neuron_type | Updates a neuron type's name, description, or file type flag. Only provided fields are changed. Requires Owner access and MCP editing to be enabled. |
| aiqbee_delete_neuron_type | Deletes a neuron type. WARNING: This action cannot be undone. If neurons exist of this type, provide reassign_to_neuron_type_id to move them to another type. Requires Owner access and MCP editing to be enabled. |
| aiqbee_create_neuron | Creates a new neuron with the specified type, name, and content. Requires ReadWrite access and MCP editing to be enabled for the brain. |
| aiqbee_update_neuron | Updates the type, name, and/or content of an existing neuron. Requires ReadWrite access and MCP editing to be enabled for the brain. |
| aiqbee_delete_neuron | Deletes a neuron from a brain. WARNING: This action cannot be undone. The neuron and all its relationships will be permanently deleted. Requires ReadWrite access and MCP editing to be enabled for the brain. |
| aiqbee_create_relationship | Creates a new directional link (synapse) from source neuron to target neuron. Both neurons must exist in the same brain. Requires ReadWrite access and MCP editing to be enabled for the brain. |
| aiqbee_update_relationship | Updates the source neuron, target neuron, and/or description of an existing relationship (synapse). Requires ReadWrite access and MCP editing to be enabled for the brain. |
| aiqbee_delete_relationship | Deletes a relationship (synapse) between neurons. WARNING: This action cannot be undone. The relationship will be permanently deleted. Requires ReadWrite access and MCP editing to be enabled for the brain. |
| aiqbee_list_users | Lists all users with access to a brain, including their email, name, access level, and when access was granted. Any user with access to the brain can call this. |
| aiqbee_grant_access | Grants access to a user for a brain by email. The user must exist in your organization. If the user already has access, their level is updated. Requires Owner access. |
| aiqbee_revoke_access | Revokes a user's access to a brain by email. WARNING: This action cannot be undone. Cannot revoke the brain creator's access. Requires Owner access. |
| aiqbee_batch_update_access | Replaces all access permissions for a brain in one operation. WARNING: Users not in the entries list will have their access REVOKED (except the brain creator). Requires Owner access. |