Connect an agent to Akera

Choose a role and access ceiling, add the hosted Streamable HTTP server, then verify its filtered tools and required skill documentation.

Before you connect

Create an agent credential in Akera under Settings → Agents. Choose Admin, Appointment Setter, or Content Writer first, then choose read-only or read-and-write access and the exact workspace grants. Akera shows the token once and generates a kickoff for that specific role.

Never paste the credential into a prompt, commit it to source control, or print it in logs. If it is exposed, revoke or rotate it immediately.

Connection settings

Configure a remote MCP server with the values below. Use the endpoint exactly as shown by Settings → Agents; do not append another /mcp path.

Use the exact role-specific server name generated by Akera: akera-funnels-admin, akera-funnels-appointment-setter, or akera-funnels-content-writer. This keeps each role in a distinct MCP tool namespace.

Content Writer MCP configuration example

{
  "name": "akera-funnels-content-writer",
  "transport": "streamable-http",
  "url": "YOUR_AKERA_MCP_URL",
  "headers": {
    "Authorization": "Bearer ${AKERA_MCP_AGENT_TOKEN}"
  }
}

Verify without changing data

Reconnect the client so it discovers the current tool list.
Call agent_bootstrap_get first and verify the agent name, role, access ceiling, workspace grants, policy and catalog versions, required skill digests, and documentation links.
Inspect the authenticated tools/list result and confirm it matches allowedTools from the bootstrap. Remembered or hidden tool names are not permission.
Browse the role-filtered MCP documentation link and the skill catalog link returned by the bootstrap. Install only requiredSkills, then read each SKILL.md and its phase-linked references.
For Admin, verify workspace_list and knowledge_get. For Appointment Setter, verify workspace_list and knowledge_get. For Content Writer, verify workspace_list, knowledge_get, and metadata-only content_article_sources_list.
Content Writer can inspect workspace knowledge and, with write access, propose a draft revision. Atomic Article work still receives Voice and strategy documents only through the enforced article context flow; generic knowledge tools cannot satisfy that receipt.
Stop if any result is unexpected. Do not use a write tool as a connection test.

Discovery stays live

This reference is generated from the running MCP server’s own tools/list response. Newly registered tools appear here after the bounded catalog cache expires; authenticated tools/list remains authoritative for a connected client.