Skip to main content

​
Overview

Aster is available as a remote MCP server. Any MCP-compatible client — Claude Desktop, Claude Code, the Claude web app, Cursor, Windsurf — can connect to Aster and, on your behalf, list and invoke your agents, search your knowledge bases, and read your conversations. Connect once and the tools appear inside your client. Sign-in uses your normal Aster login (Clerk OAuth), so the client only ever acts as you, scoped to your organization. 
https://www.asteragents.com/mcp-server
You must be a non-guest member of an Aster organization. If you can open the Control Hub in the browser, you can connect via MCP. Guests are blocked.

​
Connect a client

1

Open connector settings

In Claude, go to Settings → Connectors → Add custom connector.
2

Add the Aster URL

Paste https://www.asteragents.com/mcp-server and continue.
3

Approve access

A Clerk consent screen opens. Sign in to Aster (if needed) and approve. The connector shows connected and the Aster tools become available.
If you belong to more than one Aster organization, pass an organizationId to any tool (use list_organizations to find it). Members of a single org don’t need to — it’s resolved automatically.

​
What you can do

The server exposes a focused, read-first tool set. One tool — call_agent — runs an agent and can have side effects (it costs usage and can send email or write to knowledge bases, exactly like an in-app chat).

list_organizations

List the organizations you belong to.

list_agents

List the agents in your organization.

get_agent

Get one agent’s configuration and its tools.

list_knowledge_bases

List your organization’s knowledge bases.

search_knowledge_base

Semantic + keyword search over a knowledge base.

list_threads

List your recent conversations.

get_thread

Read a full conversation, including every message.

call_agent

Invoke an agent with a message; returns a thread you can poll.

​
Invoking an agent

call_agent runs asynchronously: it returns a threadId right away, and you poll get_thread with that id to read the reply. Pass an existing threadId to continue a conversation. Conversations started this way appear in your dashboard tagged with the source mcp, alongside chat, email, and scheduled runs.

​
Creating or editing agents and apps

There are no direct “create agent” or “build app” tools — and that’s by design. To create or modify agents, knowledge bases, or apps from your MCP client, use call_agent to talk to a builder agent in your organization (one that has the agent-building or app-building tools and skills). For example:
call_agent → your “Agent Builder” → “Create a sales-research agent that uses web search and writes findings to the Prospects knowledge base.”
The builder agent does the privileged work with its own tools and guardrails, so all validation stays where it belongs. Ask your Aster admin which builder agents are available, or see Build an Agent.

​
Security

  • You, scoped to your org. The OAuth token represents your user. Every request re-checks your organization membership live — losing access to an org immediately revokes MCP access.
  • Consent required. Connecting always shows an approval screen.
  • Guests excluded. Guest-role members cannot use the MCP server.
  • Audited. call_agent runs are recorded like any other conversation, with the source marked mcp.