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

# Connect Console through MCP

> Discover protected tools, use actual schemas and retain quote, budget and acceptance controls.

MCP lets a compatible client discover tools and call them with structured arguments. The Console MCP endpoint is separate from the public-profile and documentation MCP servers.

[Choose your client](https://docs.altss.com/agents/connect.md). Endpoint: `https://console.altss.com/v1/console/mcp`. Use an MCP-enabled Console credential or the compatible authorization-code method described in [authentication](https://docs.altss.com/console/authentication.md).

## Initialize and discover

Use Streamable HTTP. Initialize using a protocol version supported by the live server, send notifications/initialized, and then request tools/list. Follow the negotiated version and returned inputSchema rather than guessing names from capability descriptions.

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": "catalog-1",
  "method": "tools/list",
  "params": {}
}
```

The JSON-RPC body above belongs to the existing authenticated MCP transport. It is a discovery message, not a paid operation.

## Tools and structured results

The current protected server lists altss\_quote, altss\_run and altss\_get\_run. Verify these through tools/list before use. altss\_quote accepts toolId and input; altss\_run requires toolId, input, the unchanged quote, accept=true and idempotencyKey; altss\_get\_run accepts runId. Preserve structured results, evidence and charge information.

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": "quote-1",
  "method": "tools/call",
  "params": {
    "name": "altss_quote",
    "arguments": {
      "toolId": "company.financial_research",
      "input": {
        "cik": "0000789019"
      }
    }
  }
}
```

This quote example does not accept paid execution. Inspect both the HTTP status and the MCP isError field. Before calling altss\_run, present the returned quote and maximum charge for explicit purchaser acceptance.

Read the [live Console catalog](https://console.altss.com/tools.json) for each operation's availability, input and output schemas, price, billing unit and required scopes. Use the credential and quote for the intended organization before authorizing a run.

## Budget and permission controls

The organization, credential channel, scope, per-request ceiling, daily budget and funding checks remain in effect. A prompt cannot raise those limits. If the client cannot read the wallet balance through its supported tools, ask the authorized human to confirm it in Console. Do not invent a balance endpoint.

## Completion and interruption

A client disconnect or MCP cancellation notification does not cancel a paid run. Use the returned run identifier and supported retrieval tool to check state; preserve the idempotency key on retry. Do not assume that an error shown by the client proves no charge occurred.

## Separate public servers

The public server at [https://altss.com/mcp](https://altss.com/mcp) reads bounded published profiles. The docs server at [https://docs.altss.com/mcp](https://docs.altss.com/mcp) searches documentation and can write feedback to Mintlify analytics. Neither grants the protected Console credential or paid operation scope. Never send private credentials or customer records to documentation feedback.


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