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, read and write your data stores, 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.
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. Three tools have side effects: call_agent runs an agent (it costs usage and can send email or write to knowledge bases, exactly like an in-app chat), and write_data_store and manage_data_store change a data store’s rows or structure. Your client asks you to confirm those before they run.

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.

query_data_store

Run a read-only SQL query against a data store.

write_data_store

Insert, update, upsert or delete rows in a data store.

manage_data_store

Describe a data store, or add and change its tables, columns, indexes and views.

​
Working with data stores

Data stores are the knowledge bases of type structured that list_knowledge_bases returns. They’re the same stores your agents and apps use, so your client can read and keep the same data:
  1. Call manage_data_store with action: "describe" to see a store’s tables, columns and views.
  2. Read with query_data_store (any SELECT).
  3. Write with write_data_store (insert, update, upsert, delete or a batch that succeeds or fails as a whole). Updates and deletes need a filter.
A locked data store’s structure can be changed only by its creator or an org admin; its rows stay writable. Bulk loads from a file (bulk_load, sql_file) run only inside an Aster conversation, so send rows directly instead.

​
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. It also returns a threadUrl that opens the conversation in Aster, which is the link to share with a person. 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. Every data store call is logged with your user, and schema changes are recorded in the store’s change history.