AI Agents & MCP Server

Explore Córdoba runs a read-only Model Context Protocol (MCP) server. It exists so AI agents can eventually query the site's travel data directly instead of scraping rendered pages — see the Tools section below for what's actually available today. The server needs no authentication and no API key. It only reads; it cannot write or change anything.

This page is a static entry point for search engines and agent crawlers. A page alone cannot make an agent discover or connect to the MCP server. An agent, or whoever operates it, still has to read the details below and configure the connection itself.

Connect

• Endpoint: https://agents.explorecordoba.com/mcp
• Transport: Streamable HTTP (JSON-RPC 2.0 over POST)
• Discovery document: https://agents.explorecordoba.com/.well-known/mcp/server.json
• Full connection guide: https://agents.explorecordoba.com/, with connection setup and rate-limit details

The discovery document above is separate from the _mcp.explorecordoba.com DNS TXT record some agent frameworks look up first. That TXT record only points to the discovery document; it is not the MCP endpoint itself.

Any MCP client that takes a JSON config

{
  "mcpServers": {
    "cordoba": { "type": "http", "url": "https://agents.explorecordoba.com/mcp" }
  }
}

Tools

No tools are available on this server yet. A tools/list call currently returns an empty list. Check the connection guide above before assuming otherwise; this page will be updated when that changes.

Before you rely on it

• This is an early-access, experimental service meant to surface what agents actually ask for. It isn't a guaranteed data feed.
• Requests are rate-limited per network address; the server returns an HTTP 429 with a Retry-After header when a client goes over.
• Calls are logged for monitoring. IP addresses are never stored, and obvious personal data is stripped from logged arguments. Send no personal data in tool arguments regardless.