Subscribe to an API
Browse the API catalog and subscribe to the services your workflow needs. Remote MCP access is included for eligible APIs.
LATEST MCP · 2026-07-28
Bring production data APIs to the latest MCP
GuGuData Remote MCP supports the MCP 2026-07-28 protocol while remaining compatible with existing initialization-based clients. One endpoint provides automatic discovery, account-scoped tools, and secure OAuth access for AI agents.
MCP 2026-07-28Latest protocol support
Automatic negotiationOne endpoint for new and existing clients
Secure OAuthAccount-scoped authorization
Tools · Resources · Prompts A complete capability surface for agents
Quick Start
Connect in three steps
Pick an API, add the Remote MCP service to your client, and complete browser-based authorization with your GuGuData account.
Add the MCP endpoint
Configure your AI client with https://mcp.gugudata.io/mcp using Streamable HTTP transport. The client and server negotiate the protocol version automatically.
Authorize in the browser
The client opens the OAuth flow. After authorization, it can use the API tools available to the account.
MCP 2026-07-28
Built for the next generation of agents
The same Remote MCP endpoint handles version discovery and capability negotiation. Latest clients can use the new protocol directly, while existing clients retain a practical migration path.
Up-front version discovery
server/discover lets clients identify supported versions, server identity, and capabilities before making tool requests.
Stateless Remote MCP
Each request carries the context it needs, avoiding sticky protocol sessions and fitting cloud agents, horizontal scaling, and clean reconnects.
Efficient capability lists
Private cache hints for tools, resources, and prompts reduce repetitive discovery while preserving account-level isolation.
Standards-based OAuth discovery
Protected-resource discovery, Client ID Metadata Documents, and PKCE reduce manual client setup and credential handling.
Tokens scoped to the MCP service
Access tokens are issued for the GuGuData MCP resource and the authorization issuer is validated to reduce cross-service token misuse.
A practical migration path
One URL supports the latest protocol and the earlier initialize-based flow, so teams can upgrade as their MCP clients mature.
Capability
From protocol connection to real API execution
Remote MCP turns an account's existing data services into standard capabilities that agents can discover, understand, and call.
What clients get
- Original HTTP APIs remain available alongside MCP access.
- Dynamic tools for APIs available to the authorized account.
- Readable API documentation and schema references as resources.
- Prompts that help select APIs and interpret results.
- Stable ordering and cache hints for efficient capability reuse.
What GuGuData handles
- OAuth authorization without appkeys in the MCP client.
- Only available APIs are exposed to the MCP client.
- Active subscriptions are combined into one capability view.
- Automatic protocol negotiation and clean reconnection.
- Open API catalog and service health stay discoverable.
Client Config
Remote MCP endpoint
Clients that support Remote MCP and OAuth discovery can connect using this endpoint. Copy the generic JSON config as a starting point; no protocol version needs to be pinned in the configuration.
Generic MCP configuration
Works with clients that accept JSON MCP server configuration.
{
"mcpServers": {
"gugudata": {
"url": "https://mcp.gugudata.io/mcp",
"transportType": "streamable-http"
}
}
}OAuth Flow
Account-scoped authorization
The OAuth page is opened by the MCP client during connection. The page is not a standalone login shortcut.
Discovery
The client reads MCP and OAuth metadata from well-known endpoints.
Browser Login
The browser opens the GuGuData login and authorization flow.
Account Scope
GuGuData confirms the APIs available to the current account.
Client Ready
The client returns and starts using visible tools and resources.
FAQ
Common questions
These answers cover pricing, availability, and credential handling for Remote MCP clients.
Does GuGuData support the latest MCP protocol?
Yes. GuGuData Remote MCP supports MCP 2026-07-28, including server/discover, stateless requests, and cache-aware capability lists.
Will existing MCP clients continue to work?
The service negotiates the protocol based on client capabilities and supports the earlier initialize-based flow. Exact behavior still depends on the MCP version implemented by each client.
Does Remote MCP cost extra?
No. Remote MCP is included for eligible APIs you already subscribe to on GuGuData, while the original HTTP API remains available.
How are multiple subscriptions handled?
The client sees the API capabilities available to the authorized GuGuData account. Existing HTTP API access continues to work.
Why do I only see some tools in the client?
The client only sees API tools available to the authorized account. Browse the API catalog to add more services when your workflow needs broader coverage.
Do I need to paste an appkey into the MCP client?
No. The client uses OAuth authorization instead of manual appkey handling.
What happens if the connection is interrupted?
The latest protocol uses stateless requests, so a client can create a clean connection and discover capabilities again. If an operation was interrupted before its response completed, retry behavior depends on the client and the operation itself.
START NOW
Give your agent governed access to production data
Choose the APIs your workflow needs, then connect one Remote MCP endpoint and authorize with your GuGuData account.