Connect tools with API & MCP

Connect one project at a time

Select the project, open your profile menu and choose Connected tools. The page is titled Connected tools, with Connect an MCP tool and Build with the Astor API. API keys and application connections belong to one person and one project. Current membership, role, granted permissions and expiry are checked on every call.

Choose only the permissions the tool needs. Removing the member or revoking the connection stops further access; linking a tool does not broaden the person’s project role. Human ticket decisions deliver subscribed events for that project separately from AI processing. Retry and expiry checks still apply.

Use the REST API

Under Build with the Astor API, choose Create an API key. Name the key, choose permissions and expiry, and store the value shown once. Send it in the Authorization header, not in a URL. Copying is optional: select the displayed key if browser copying is unavailable. A new copy attempt clears the earlier copy message.

curl https://astor.sh/api/v1/profile \
  -H "Authorization: Bearer $ASTOR_API_KEY"

The base URL is https://astor.sh/api/v1. Read the generated API reference or download OpenAPI.

API-key creation and connection approval recheck your current sign-in before saving. Signing out or an expired session stops a request that is still receiving its data; sign in again before retrying.

Writes use a UUID idempotency key. If the result is uncertain, retry the same operation, resource and payload with the same key while your access is unchanged. Editing also requires the current version or revision. A stale version, changed permissions or a key reused for another request can return 409. Reload the current item and check whether the change was already saved before starting a new operation. Older request references whose original access cannot be checked are also refused; retrying cannot restore removed permissions.

REST settings, project context, activity and subscription writes recheck the connection after receiving the request. Revoking the connection or changing its role, project scope or granted permissions stops the earlier request, including a cached retry. Reconnect with the permissions the operation needs before trying again.

Ticket writes check the current session or connection after receiving the request. A cached retry also requires the ticket to remain visible. Revoked connections, removed project access and withdrawn tickets cannot return an earlier private reply.

Ordinary reads and edits use no AI capacity. An explicit analysis or project-enabled background review can reserve capacity; inspect the profile, work quote and applicable operation before starting.

For analyse_ticket, an empty message requests a new six-unit review. A nonempty message answers current saved open questions within an already accepted review, with no new units. Read analysis.canFollowUp and analysis.followUpQuestions from get_ticket; send its current analysis.id as analysis_id when answering. A first, resolved or changed review cannot authorize an included reply. A saved answer that reaches the shared estimated cost ceiling returns a blocked review with the answer retained; no new model attempt or paid fallback starts. API and MCP use these same server checks and current project access.

Mission writes also check current access after receiving the request, before returning a cached retry. Revoked access cannot create or start a Mission, add steps or save a result. A permitted person can save their own written Mission result with no AI capacity remaining; saving it does not start analysis.

Connect an MCP application

Use https://astor.sh/mcp with an application that supports Astor’s advertised MCP version, currently 2026-07-28. Sign in, choose one project and review its permissions. HTTPS address available describes the endpoint, not a verified ChatGPT, Claude or builder connection. Check the tool’s compatibility before connecting. OAuth access tokens are for MCP; REST uses API keys. Never paste an API key into a public ticket.

Start with read access to inspect project context and feedback. Grant write access when you want to save a draft or report an updated version. Reading and manual edits use no AI units. A connection gives access to Astor; it does not make your ChatGPT or another provider’s model subscription available to the project.

For paid analysis, inspect get_work_quote and confirm the bounded work before starting. A zero balance does not prevent manual ticket creation. Retry the same saved request with its original idempotency key while your access is unchanged; a saved draft is not an approved scope or a verified improvement.

Connections use one-time sign-in codes and rotating access tokens. An already-used code cannot issue another token. Reusing a refresh token revokes the connection; reconnect the tool if this happens.

The generated MCP reference lists the actual supported tools and their inputs. A catalog entry does not mean a particular connection can execute it: current access checks still apply.

For a building tool, get_ticket returns the current brief and a separate approved_brief when scope is approved. Use approved_brief.brief for implementation and check that approved_brief.version equals scope_version. If that package is absent or cannot be read, review the ticket in Astor before proceeding. Copy implementation brief uses the same locked version and remains available without a connected tool.

After making the change, add_updated_version uses the current ticket version and records what changed, test instructions and a release or preview reference. This is a reported result; a person still verifies the agreed checks before closing the ticket.

Product events

The API can read an event feed and manage supported webhook subscriptions. Verify the subscriber challenge and signatures, handle retries idempotently and retain the event cursor. The current event catalog is ticket-focused; do not assume every Mission or external action emits a webhook.

Connected tools shows pending and failed recent deliveries without opening the history. Open Recent deliveries for saved states, attempts and recorded update times. Delivered means the callback accepted the event; it does not confirm that the connected tool acted on it or that a person verified the result.

A tool can help draft, investigate or implement. Human review, project boundaries and ticket verification still apply.

Public discovery

Astor's discovery file links to public guides, the price catalog, API contract and MCP tool contract. These references can be read without JavaScript or signing in. Private project data still requires the authenticated project access described above; discovery grants no permissions.