Reference

MCP client setup

Astrail-hosted MCP endpoints expose a small HTTP JSON-RPC surface. Start with initialize and tools/list, then call reviewed tools through tools/call.

Updated Jun 25, 20265 min read

Implementation

Path to ship.

Copy the MCP endpoint URL from the generated server.

Add an Authorization bearer token when the server is private.

Call initialize, then tools/list to inspect the available surface.

Call tools/call with validated arguments and inspect the structured response.

Guide

Connection model

Hosted MCP keeps the server online for agents that can call HTTP endpoints. That avoids local process setup for early testing and gives teams one place to review logs, credentials, and generated metadata.

The same endpoint can also feed SDK exports when a team needs code ownership.

Guide

What to test first

Test initialize, tools/list, a harmless public read call, and an auth-required call. The expected result for missing credentials should be explicit rather than a vague upstream error.

After that, verify trace ids and logs so the team can debug real agent behavior.

FAQ

Common questions.

What transport does Astrail use for hosted MCP?

Astrail exposes hosted MCP over HTTP JSON-RPC for initialize, tools/list, tools/call, search_docs, and execute.

Do private servers need a bearer token?

Yes. Private MCP servers should be called with an Astrail API key in the Authorization header.