# Oro Intel MCP server

Oro Intel exposes the same metered data layer as a streamable-HTTP MCP server, so an
agent can call it as tools. Endpoint: `https://api.oro-intel.com/mcp/`.

## Keep the trailing slash

The MCP URL must end in a **trailing slash** — `https://api.oro-intel.com/mcp/`.
Without it the transport won't connect. Authentication is the same bearer API key as the
REST API, sent as a header.

## Add to Claude Code

```
claude mcp add --transport http oro-intel https://api.oro-intel.com/mcp/ \
  --header "Authorization: Bearer oro_YOUR_KEY"
```

If the command drops the header (a shell line-continuation can swallow it), add the
server directly to `~/.claude.json` under `mcpServers`:

```json
"oro-intel": {
  "type": "http",
  "url": "https://api.oro-intel.com/mcp/",
  "headers": { "Authorization": "Bearer oro_YOUR_KEY" }
}
```

## Tools

The MCP tools mirror the REST endpoints one-to-one and carry the same credit costs (see
the REST API reference): `oro_search_notices`, `oro_search_tenders`,
`oro_lookup_contract`, `oro_contract_documents`, `oro_lookup_company`,
`oro_company_contracts`, `oro_company_profile` (flagship), `oro_lookup_buyer`,
`oro_buyer_contracts`, `oro_buyer_profile`, `oro_lookup_framework`, `oro_bulk_export`,
`oro_get_balance`. Each tool description states its cost so the agent knows before it
calls.