> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asteragents.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Aster MCP Server

> Connect Claude, Cursor, and other MCP clients to your Aster agents, knowledge bases, and conversations

## 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
```

<Note>
  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.
</Note>

## Connect a client

<Tabs>
  <Tab title="Claude Desktop / Claude web">
    <Steps>
      <Step title="Open connector settings">
        In Claude, go to **Settings → Connectors → Add custom connector**.
      </Step>

      <Step title="Add the Aster URL">
        Paste `https://www.asteragents.com/mcp-server` and continue.
      </Step>

      <Step title="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.
      </Step>
    </Steps>
  </Tab>

  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http aster https://www.asteragents.com/mcp-server
    ```

    Claude Code walks you through the OAuth sign-in the first time you use it.
  </Tab>

  <Tab title="Cursor / other clients">
    Add a remote MCP server of type **HTTP** with the URL
    `https://www.asteragents.com/mcp-server`. The client discovers the OAuth flow
    automatically and prompts you to sign in.
  </Tab>
</Tabs>

<Note>
  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.
</Note>

## 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).

<CardGroup cols={2}>
  <Card title="list_organizations" icon="building">
    List the organizations you belong to.
  </Card>

  <Card title="list_agents" icon="robot">
    List the agents in your organization.
  </Card>

  <Card title="get_agent" icon="gear">
    Get one agent's configuration and its tools.
  </Card>

  <Card title="list_knowledge_bases" icon="book">
    List your organization's knowledge bases.
  </Card>

  <Card title="search_knowledge_base" icon="magnifying-glass">
    Semantic + keyword search over a knowledge base.
  </Card>

  <Card title="list_threads" icon="comments">
    List your recent conversations.
  </Card>

  <Card title="get_thread" icon="message">
    Read a full conversation, including every message.
  </Card>

  <Card title="call_agent" icon="paper-plane">
    Invoke an agent with a message; returns a thread you can poll.
  </Card>
</CardGroup>

### 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](/features/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`.
