What authentication does Aiqbee Brain use?
Aiqbee Brain uses OAuth 2.0. No API keys are needed.
@AIQBee
Basic information
AI knowledge graph for architecture, portfolio, and digital strategy management. 25 MCP tools to manage brains, neurons, relationships, neuron types, and access control. OAuth 2.0 authenticated, remote hosted.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"aiqbee": {
"url": "https://mcp.aiqbee.com/mcp",
"type": "streamable-http"
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
This server requires authentication. Tool discovery may require signing in or credentials from the provider.
Fetch the live tool list directly from this server's endpoint using the button above.
Aiqbee Brain connects AI assistants to your Aiqbee knowledge graph. It allows you to search, create, and link neurons across your architecture, portfolio, and digital strategy brains.
Configure your MCP client to connect to the remote server at https://mcp.aiqbee.com/mcp using OAuth 2.0. No API keys are required.
Aiqbee Brain uses OAuth 2.0. No API keys are needed.
Aiqbee Brain is a remote server available via streamable HTTP at `https://mcp.aiqbee.com/mcp`.
You can search, create, and link neurons across knowledge graphs for enterprise architecture, portfolio management, and digital strategy.
Aiqbee Brain provides 25 MCP tools covering brain management, search, neurons, relationships, neuron types, and access control.

Model Context Protocol Servers
🚀 The fast, Pythonic way to build MCP servers and clients.

Connect your AI assistant to your own YOUB endurance training account. Read recorded activities with full analysis, planned sessions, race goals, wellness (HRV, sleep, resting HR) and your athletic profile. Create or mov

Model Context Protocol Servers

B2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.
Comments