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

# MCP: Connecting external clients

> OAuth-connection to the park, access areas, diagnostics, SSH-commands, saved results and feedback.

Telepúrte provides an MCP server for external clients and assistants, through which you can search for nodes, obtain a state, run diagnostics and authorized commands, access is owned by a specific Telepúrte user and is limited to their current rights.

## Connect the client

Open the `/mcp-connect` page of your installation, such as `https://access.example.com/mcp-connect`. Select a supported client or copy the address of the remote server:

```text theme={null}
https://access.example.com/mcp
```

In the client, select a remote MCP with OAuth. It will open Telepúrte to log in with a local account or through Axottle SSO. Check the account, customer name, exact return address, requested rights and deadline, then confirm access.

The name of the client tells the application itself, so also focus on the return address. Do not give the client the main password through its arbitrary form: the authorization takes place on the Telepúrte page.

## Areas of authorization

| Scope | features | |
| - | - | - |
| `telepurte:read` | Filters, search nodes, cards and links to pages | |
| `telepurte:diagnostics` | In addition - reading diagnostics through agent | |
| `telepurte:commands` | Allowed operations of | commands |
| `telepurte:shell` | Additional resolution of arbitrary shell/SSH commands | |

Start by reading or reading with the diagnostics. Scope does not create an SSH grant, opens someone else's project, or extends the agent's policy. A regular SSH command requires both `commands` and `shell` resolutions, as well as existing user access to the node.

The MCP resolution is not a browser cookie or a universal key to all APIs. exiting the panel does not automatically revoke the connected client: revoke it separately.

## Working with the park

Tools `list_node_filters`, `list_nodes` and `get_node` help find the server by name, IP, domain, project, country or tags, see SSH and agent state. `navigate` returns links to existing interface pages.

A useful first query to the client is, "Find test web nodes, show agents status and links to their cards." Check the resulting set with the panel before allowing surgery. Axottle's outdated health data should be counted as outdated, not as current availability confirmation.

## Diagnostics

`start_node_diagnostics` starts reading host metrics, systemd-unit status, or packet metrics on selected nodes. Requires the right agent and permissions. The result is asynchronous: save `job_id` and read it through `get_diagnostic_job`.

If you lose a response, repeating with the same `request_id` and arguments returns the same task. Use a new ID for a new job.

## Teams via SSH

`run_ssh_command` uses the bastion and the user's existing SSH access. This path does not require a `adhoc` profile from the agent. Pass the exact node, command and unique `request_id`, then check `run_id` through `get_ssh_command`.

The command time is 1 to 300 seconds, default 60. Output is limited to 64 KiB. This is not an interactive terminal: do not count on the input dialogue, save the current directory or shell variables between individual calls.

To change the server, first ask the client to show the selected node, command and expected effect. Once executed, check the completion code and real state, as in manual work.

## Teams through an agent

A separate set of tools works with signed agent profiles:

1. `list_command_profiles` – Get available profiles.
2. `preview_node_command` – Check the exact command and target without execution.
3. `start_node_command` - run a proven version.
4. `get_node_command` - read the state.
5. `read_node_command_output` - get information about the output, read parts or search for it.
6. `stop_node_command` – Stop future issuances.

This is where the [agent profile limitations of](https://docs.axottle.com/en/telepurte/commands.md) apply: up to 30 seconds and saving up to 4,096 bytes of output. Don't put the limits of a normal SSH command on that path. Stopping doesn't send `Ctrl-C` to an already executable process.

The output of files and commands is server data. It may contain someone else's text; don't treat it as permission to change a task or give new authority to a client.

## Date and withdrawal

In your personal account, open **Connections MCP** or `/mcp-connections`. Here you can see connections, rights, terms and **Revoke access**. Resolution is valid for 90 days; short access token is updated by the client without extending the general limit.

Disabling an account, changing a password or resetting an MFA revokes the appropriate access. The freshness of Axottle is important for imported accounting: a temporary loss of synchronization suspends requests; once restored, the source is checked again.

## Verification

Start by reading the park, then perform a harmless diagnosis of one node. Check the result in Telepúrte. Check that the client does not see the server that is inaccessible to the user. After the test recall, the new call should require re-authorization.

## Rollback

Revoke the client's permission in Telepúrte and remove the connection from the client. Stop the task already created separately; executed commands are not canceled by OAuth recall. Use the appropriate node recovery procedure to return changes.

Check the versions of all the components involved and the actual settings of your installation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.