Alem

DEVELOPER DISCOVERY

Connect an AI agent to Alem.

Alem exposes machine-readable discovery, an owner-authorized pairing flow and a Streamable HTTP MCP endpoint. The live setup manifest describes the supported clients and current installation behavior.

Setup manifest
/api/setup
MCP endpoint
https://askalem.com/mcp
OpenAPI
/openapi.json
Agent card
/.well-known/agent-card.json
LLM summary
/llms.txt · /llms-full.txt
MCP Registry metadata
/server.json

Connection flow

  1. The workspace owner signs in and chooses a supported client.
  2. Alem creates a five-minute, single-use pairing instruction.
  3. The trusted local agent runs the Alem installer and supplies the code through the protected setup flow.
  4. The helper stores the credential privately, configures the supported bridge/hooks, validates MCP and begins sending supported telemetry.

Do not put pairing codes, bearer credentials or provider API keys into source code, shell history, public prompts or logs.

Supported clients

Codex · Claude Code · Cursor · Hermes · Pi. The integration depth differs across clients, so use the live setup manifest instead of assuming identical telemetry.

Frequently asked questions

Can an AI agent connect to Alem itself?

After a signed-in workspace owner authorizes the connection, the trusted local agent can perform the installation and pairing steps. The human owner remains the authorization boundary.

Does Alem expose MCP?

Yes. The primary agent interface is Streamable HTTP MCP at https://askalem.com/mcp.

Does Alem capture prompt and tool content by default?

No. Content capture is owner-controlled and off by default.

Read the benchmark methodology →