streamable-httpupdated 2mo ago
UK public procurement data for AI agents β tenders, contracts, buyer and supplier profiles over MCP and REST. 250 free credits.
What can you do with oro intel mcp?
Oro Intel MCP β UK Public Procurement Data for AI Agents
UK public procurement data for AI agents β tenders, contracts, buyer and supplier profiles over MCP and REST. 250 free credits.
Give any AI agent live UK public-sector procurement data β tender notices, awarded contracts, buyer (council/department) and supplier profiles β over MCP or a plain REST API. Same account, same credits, both transports. Charged on success only.
- What it covers: UK Contracts Finder + Find a Tender notices, awarded contracts and their documents, company/supplier profiles, buyer profiles, frameworks, bulk export.
- Who it's for: agent builders, procurement/bid-writing tools, market-intelligence and govtech apps.
- Remote & hosted: nothing to run locally. Point your client at the URL.
- Auth: sign in with OAuth (interactive clients β no key to copy), or send an
API key as
Authorization: Bearer oro_...(headless agents and scripts).
60-second quickstart
- Interactive client (Claude, ChatGPT, Cursorβ¦): add the server below and sign in when prompted β done. Headless/scripts: create a key at https://app.oro-intel.com/dashboard/developers (shown once).
- Add the server to your client (matrix below).
- Ask: "search UK tenders for EV charging in the last 30 days."
Install
Endpoint:
https://api.oro-intel.com/mcp/β keep the trailing slash. Interactive clients: OAuth sign-in, no header needed. Headless: headerAuthorization: Bearer oro_YOUR_KEY.
claude mcp add --transport http oro-intel https://api.oro-intel.com/mcp/
Sign in in the browser window that opens (or run /mcp β oro-intel β
Authenticate). For headless use, pass a key instead:
claude mcp add --transport http oro-intel https://api.oro-intel.com/mcp/ \
--header "Authorization: Bearer oro_YOUR_KEY"
If the header is dropped, add to ~/.claude.json under mcpServers:
"oro-intel": {
"type": "http",
"url": "https://api.oro-intel.com/mcp/",
"headers": { "Authorization": "Bearer oro_YOUR_KEY" }
}
Settings β Connectors β Add custom connector. Name it Oro Intel, paste
https://api.oro-intel.com/mcp/, click Add, sign in when prompted.
Or edit claude_desktop_config.json:
{ "mcpServers": { "oro-intel": {
"type": "http",
"url": "https://api.oro-intel.com/mcp/",
"headers": { "Authorization": "Bearer oro_YOUR_KEY" } } } }
Settings β MCP β Add new MCP server, or .cursor/mcp.json
(project) / ~/.cursor/mcp.json (global):
{ "mcpServers": { "oro-intel": {
"url": "https://api.oro-intel.com/mcp/",
"headers": { "Authorization": "Bearer oro_YOUR_KEY" } } } }
Omit headers to use OAuth sign-in instead.
~/.codeium/windsurf/mcp_config.json:
{ "mcpServers": { "oro-intel": {
"serverUrl": "https://api.oro-intel.com/mcp/",
"headers": { "Authorization": "Bearer oro_YOUR_KEY" } } } }
.vscode/mcp.json:
{ "servers": { "oro-intel": {
"type": "http",
"url": "https://api.oro-intel.com/mcp/",
"headers": { "Authorization": "Bearer ${input:oro_key}" } } },
"inputs": [ { "type": "promptString", "id": "oro_key",
"description": "Oro Intel API key", "password": true } ] }
Settings β Apps & Connectors β Advanced settings β Developer mode (Plus/Pro),
then Create connector with MCP server URL https://api.oro-intel.com/mcp/.
Choose OAuth and sign in when prompted. (Remote streamable-HTTP only.)
codex mcp add oro-intel --url https://api.oro-intel.com/mcp/
Or ~/.codex/config.toml:
[mcp_servers.oro-intel]
url = "https://api.oro-intel.com/mcp/"
~/.gemini/settings.json:
{ "mcpServers": { "oro-intel": { "httpUrl": "https://api.oro-intel.com/mcp/" } } }
Restart the CLI and sign in in the browser window that opens on first use.
Any client that supports remote streamable-HTTP MCP works: URL
https://api.oro-intel.com/mcp/, and either OAuth sign-in or the header
Authorization: Bearer oro_YOUR_KEY.
"oro-intel": {
"type": "http",
"url": "https://api.oro-intel.com/mcp/",
"headers": { "Authorization": "Bearer oro_YOUR_KEY" }
}
Tools
The MCP tools mirror the REST API one-to-one and carry the same credit costs. Each tool description states its cost, so the agent knows before it calls. 1 credit = Β£0.01.
| Tool | What it returns | Credits |
|---|---|---|
oro_search_notices |
Search tender/contract notices | 2 |
oro_search_tenders |
Search live (open) tenders | 2 |
oro_lookup_contract |
Full record for one notice/contract | 5 |
oro_contract_documents |
Documents attached to a contract | 10 |
oro_lookup_company |
Resolve a company name β record | 5 |
oro_company_contracts |
Contracts a company has won | 10 |
oro_company_profile |
Flagship β full supplier profile: core record + every contract won, one call | 12 |
oro_lookup_buyer |
Resolve a buyer (council/dept) name β record | 5 |
oro_buyer_contracts |
Contracts a buyer has issued | 10 |
oro_buyer_profile |
Full buyer profile | 20 |
oro_lookup_framework |
Framework agreement record | 5 |
oro_bulk_export |
Bulk pull for a query | 100 / 1,000 rows |
oro_get_balance |
Remaining credits | free |
Auth & credits
One account covers both API and MCP. 250 free credits on signup; 1 credit =
Β£0.01. Charged on success only β an empty lookup isn't billed. Pass an
Idempotency-Key header so retries never double-bill. Out of credits β
402 insufficient_credits with a top_up_url in the body.
Every metered response echoes credits_charged and credits_remaining.
Also available as a REST API
Prefer plain HTTP? Same data, same key: https://api.oro-intel.com/v1/*
(OpenAPI 3.1: https://api.oro-intel.com/openapi.json).
curl -s "https://api.oro-intel.com/v1/companies/search?name=Serco" \
-H "Authorization: Bearer $ORO_API_KEY"
Examples
Runnable snippets in /examples: curl Β· Python Β· JavaScript Β·
LangChain Β· LlamaIndex Β· OpenAI function calling Β· Vercel AI SDK Β· PydanticAI.
Every example runs the flagship flow β resolve a company by name, then fetch its
full profile β and prints credits_charged / credits_remaining.
Links
Docs https://documentation.oro-intel.com Β· MCP guide https://documentation.oro-intel.com/docs/mcp Β· Quickstart https://documentation.oro-intel.com/docs/quickstart Β· Agents start here https://documentation.oro-intel.com/llms.txt Β· Status https://documentation.oro-intel.com/docs/status Β· Changelog CHANGELOG.md
Install
Add oro intel mcp to your client. Pick the one you use.
claude mcp add --transport http oro-intel-mcp https://api.oro-intel.com/mcp/codex mcp add oro-intel-mcp --url https://api.oro-intel.com/mcp/{
"mcpServers": {
"oro-intel-mcp": {
"url": "https://api.oro-intel.com/mcp/"
}
}
}Add to `~/.cursor/mcp.json`, or `.cursor/mcp.json` for a single project.
{
"servers": {
"oro-intel-mcp": {
"type": "http",
"url": "https://api.oro-intel.com/mcp/"
}
}
}Add to `.vscode/mcp.json` in your workspace.
{
"mcpServers": {
"oro-intel-mcp": {
"url": "https://api.oro-intel.com/mcp/"
}
}
}Add to `claude_desktop_config.json`, then restart Claude Desktop.
{
"mcpServers": {
"oro-intel-mcp": {
"serverUrl": "https://api.oro-intel.com/mcp/"
}
}
}Add to `~/.codeium/windsurf/mcp_config.json`.
13 tools
oro intel mcp exposes 13 tools to a connected agent.
- oro_search_notices
- Search tender/contract notices
- oro_search_tenders
- Search live (open) tenders
- oro_lookup_contract
- Full record for one notice/contract
- oro_contract_documents
- Documents attached to a contract
- oro_lookup_company
- Resolve a company name β record
- oro_company_contracts
- Contracts a company has won
- oro_company_profile
- **Flagship** β full supplier profile: core record + every contract won, one call
- oro_lookup_buyer
- Resolve a buyer (council/dept) name β record
- oro_buyer_contracts
- Contracts a buyer has issued
- oro_buyer_profile
- Full buyer profile
- oro_lookup_framework
- Framework agreement record
- oro_bulk_export
- Bulk pull for a query
- oro_get_balance
- Remaining credits
Score
67 / 100
Good
- Documentation25/25
- Maintenance16/25
- Trust6/20
- Capability8/15
- Install experience12/15
- Documents what it does and how to connect
- Has a resolvable package or endpoint
- Exposes at least one tool, prompt or resource
- README has substantive content
- Includes a code example
- Documents its configuration
- Mentions credentials or security posture
- Last commit 60 days ago
- Has a release history
- Repository is not archived
- No licence detected
- Namespace verified in the official MCP registry
- Claimed by its owner
- Published under an organisation
- 13 tool(s) documented
- Provides prompt templates
- Provides resources
- 6 documented install method(s)
- Published to a package registry
- Offers a hosted endpoint β no local install
Version history
| Versions | Published |
|---|---|
| 1.0.0Latest | Jul 3, 2026 |