MCP transports
Choose the transport supported by your client and supply the authentication it requires.
Streamable HTTP (recommended)
Connect MCP client sessions to https://mcp.fenceline.ai/mcp. Discovery
requests — initialize, resources/list, resources/read — are open without credentials, so any
client can read the server guide before authenticating.
JSON-RPC over HTTP
https://mcp.fenceline.ai/mcp/rpc serves stateless compatibility requests for clients that
don't hold a session. Discovery is open here as well.
Server-Sent Events
https://mcp.fenceline.ai/mcp/sse supports legacy streaming sessions and requires an API
key to connect. Prefer Streamable HTTP for new integrations.
stdio (local development)
The local transport runs the server from a repository checkout for protocol and tool development. See local client development for setup.
Authentication
The API-key endpoints listed above accept X-API-Key or a bearer token and
validate the supplied API key. Tool access is enforced through the hierarchical mcp:read, mcp:write, mcp:internal, and mcp:admin scopes. Ask your
administrator to issue or revoke keys through the account’s key-management controls.