Your clusters. Your AI tools.

A direct line from
AI to your edge.

Connect your AI tools to Approximated using the Model Context Protocol (MCP).

Investigate traffic, check a custom domain, or manage its configuration. You choose the clusters and the actions your tool can access.

Set up MCP Read the connection guide

For your existing Approximated clusters.

A connection you control
Your AI toolConnected with OAuth or a personal token
Selected clusterProduction
Traffic analytics
Read
Custom domains
Read
Configuration changes
Not granted
Staging clusterOutside this connection’s scope
Illustrative example · you select the scope and permissions.

From a question to the details

Bring your infrastructure
into the conversation.

Give your AI tool access to the information and operations it needs, without handing it every permission.

Understand your traffic

Explore request volume, latency, and traffic breakdowns. Read available request logs and traces to investigate what happened on a cluster or domain.

Try asking

“Which domains had the most errors in the last hour?”

Read permissions

Get a domain connected

Inspect custom domains, look up DNS records, and check DNS and SSL status. With the relevant write permissions, create domains or update their upstreams.

Try asking

“Show the latest DNS and SSL status for shop.example.com.”

Read permissions

Work with your edge configuration

Inspect webhooks, Edge Verify rules, and edge sequences. Grant create, update, or delete permissions separately when your workflow needs to change them.

Try asking

“List the edge sequences configured for Production.”

Read permissions

These prompts are examples. Available tools depend on the permissions you grant; traffic data depends on your cluster’s available history.

Scope before you connect

Useful access.
Clear boundaries.

Start with read access for an investigation. Add specific write actions when you want your AI tool to make changes.

You choose the clusters
Allow the connection to access selected clusters, or all clusters available to you.
Reads and writes are separate
Create, update, and delete actions require their own grants. A read-only connection cannot change configuration.
Access follows your membership
Cluster access is checked against your current membership on every call. A connection cannot keep access to a cluster you have left.
You can revoke the connection
Revoke a personal token or an OAuth connection from the dashboard when it is no longer needed.

Two ways to connect

Use the setup your tool supports.

Choose an MCP client that supports a remote server and one of the authentication methods below.

Connect with OAuth

For clients that support remote MCP with OAuth. Add the server URL, then sign in to Approximated to select clusters and authorize permissions.

MCP server URLhttps://cloud.approximated.app/mcp
Follow the OAuth setup

Use a personal token

For clients that support bearer-token authentication. Create a token in the dashboard’s MCP settings, select its clusters and permissions, then configure it in your client.

Dashboard → MCP

A separate token for each tool makes its access easier to manage and revoke.

Open MCP settings

Your client handles how you ask questions and run tools.
Approximated enforces the access you grant.

Explore the MCP documentation