Skip to main content
Configuration format verified against the client’s documentation; a funded, authorized Console connection is still required.

Prerequisites

  • A Console-issued credential with company.read, the MCP channel and approved spending limits.
  • A client version supporting remote Streamable HTTP and a private Bearer header.
Complete Console onboarding before protected paid use.

Connection steps

  1. Use a project .mcp.json or your approved user-level MCP configuration.
  2. Set ALTSS_CONSOLE_API_KEY privately in the client environment. Do not put its value in the JSON file.
  3. Save the configuration in the client’s supported MCP settings and reconnect the server.
  4. Inspect the tool list and input schemas. Confirm the expected Console host and organization before using a paid tool.
  5. Paste the instructions below and supply your specific research objective and budget.

Copy configuration

Agent instructions

Verify the connection

Inspect the live tool inventory and schema before quoting work. Keep the organization, permitted inputs, maximum charge and actual run/settlement separate. A successful connection is not a payment or an accepted execution.

References

Protocol guide · Specialized prompts