Akb

Please install the `akb` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Node.js** — Required to run the published `akb-mcp` stdio proxy via npm/npx. (https://www.npmjs.com/package/akb-mcp/"},{"title":"Provision or access an AKB server","description":"The MCP proxy connects to an AKB backend over Streamable HTTP. You can use the public demo or a self-hosted AKB deployment.","command":null,"link":"https://akb-demo.agent.seahorse.dnotitia.ai"},{"title":"Obtain an AKB Bearer token / API token","description":"The README states custom agents connect to the HTTP MCP endpoint with a Bearer token. You need a token for the target AKB server.","command":null,"link":null}],)
- **AKB server base URL** — Base URL of the AKB deployment that the stdio proxy should forward MCP requests to.
- **AKB MCP endpoint URL** — Full Streamable HTTP MCP endpoint. The README shows `/mcp/` on the AKB server.

Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","akb-mcp","--url","<your-akb-mcp-url>","--token","<your-bearer-token>"]

Note: AKB supports both Streamable HTTP and stdio. For MCP clients, prefer the published `akb-mcp` npm stdio proxy as the simplest portable path. The README explicitly says Cursor, Windsurf, Cline, and Continue use the `akb-mcp` stdio proxy, and says to point it at `https://<server>/mcp/`. If you self-host AKB, backend runtime configuration is done in `config/app.yaml` and `config/secret.yaml` on the server side, not via MCP client env vars.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.