AutoUncle Data Services is in beta. The API, MCP tools and agent skill may change often, including breaking changes, until version 1.0. Read the changelog before you upgrade an integration.
Other MCP clients
Any MCP client that speaks Streamable HTTP can use the Data MCP server. For clients that only run local (stdio) servers, use a bridge such as mcp-remote. To inspect the server by hand, use the MCP Inspector.
Streamable HTTP clients
Configure a remote server with:
| Setting | Value |
|---|---|
| URL | https://data-services.autouncle.com/mcp |
| Transport | Streamable HTTP (not SSE) |
| Header, API key | Authorization: Bearer au_test_... (or a live key) |
| OAuth | Discovered from the 401 response; see OAuth or API key |
What the server expects and returns:
- Every JSON-RPC message is a
POSTwithContent-Type: application/jsonandAccept: application/json, text/event-stream. - Responses are
application/json. - The server is stateless: it issues no
Mcp-Session-Id, andtools/callworks without a priorinitialize. Clients that sendinitializereceive protocol version2025-06-18. - Authentication failures return HTTP
401withWWW-Authenticate: Bearer resource_metadata="https://data-services.autouncle.com/.well-known/oauth-protected-resource/mcp"and a JSON-RPC error whosedatais a Problem.
You can try this with curl; see test the endpoint directly.
mcp-remote for stdio-only clients
mcp-remote runs locally as a stdio server and forwards to the remote endpoint. Use it in any client that can start a command:
{
"mcpServers": {
"autouncle-data": {
"command": "npx",
"args": ["mcp-remote", "https://data-services.autouncle.com/mcp", "--header", "Authorization:${AUTH_HEADER}"],
"env": { "AUTH_HEADER": "Bearer au_test_..." }
}
}
}
- Write
Authorization:${AUTH_HEADER}without a space after the colon. Some clients mangle spaces inside arguments; keeping the space in the environment value avoids that. - Without
--header,mcp-remoteruns the OAuth flow in your browser. mcp-remotetries Streamable HTTP first by default.
MCP Inspector
The MCP Inspector shows the tools and lets you call them by hand.
npx @modelcontextprotocol/inspector
This opens a web UI: choose the Streamable HTTP transport, enter the URL and add the Authorization header. From the command line:
npx @modelcontextprotocol/inspector --cli --transport http \
--server-url https://data-services.autouncle.com/mcp \
--header "Authorization: Bearer $AUTOUNCLE_API_KEY" --method tools/list
Pin the Inspector's version when you use it in CI.
Verify the connection
Call get_account. It takes no arguments and returns your workspace, the key's mode and scopes, and your remaining credits.
Sources: MCP Streamable HTTP transport, mcp-remote, MCP Inspector.