API Tools
abundera.ai
Provides search, description, and execution of Abundera API operations.
ENDPOINT 1
https://abundera.ai/mcp
MCP server metadata
- Name
- abundera-api
- Version
- 1.0.0
Abundera API MCP server (302 operations + curated hub tools). Curated tools cover the common hub flows: whoami, list_products, get_capabilities, list_api_keys, list_webhooks, create_api_key. For the long tail use search_operations to find an operation, describe_operation for its schema, invoke_operation to call it. Discovery (initialize, tools/list, search_operations, describe_operation) is open; calling any curated tool or invoke_operation requires a credential — an OAuth 2.1 access token (aud https://abundera.ai/mcp, from /.well-known/oauth-authorization-server) or an API key (Bearer abnd_live_… from Settings → API keys). Write tools need the mcp:abundera:write scope. The credential is forwarded to every call; cookies never are. Responses follow the { ok, data, error, request_id } envelope. Reference docs: https://abundera.ai/docs/
Known tools 9
whoamiReturn the authenticated account's identity and profile (id, email, display name, role, status, auth method).
Potential side effectslist_productsList the products in the Abundera registry (id, name, dashboard + docs URLs, and each product's live capability catalog).
Inferred read-onlyget_capabilitiesReturn the hub's capabilities document (API scopes, webhook event types, rate-limit tiers) from /.well-known/abundera-capabilities.json.
Inferred read-onlylist_api_keysList the current account's API keys (prefix, name, IP restrictions, usage metadata).
Inferred read-onlylist_webhooksList the current account's webhook endpoints (id, url, subscribed events, status).
Inferred read-onlysearch_operationsSearch this product's API operations by keyword, tag, or HTTP method.
Inferred read-onlydescribe_operationFull detail for one operation: HTTP method, path, auth requirements, path/query parameters, and the request-body JSON schema, everything needed to construct an invoke_operation call.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.abundera-api]
url = "https://abundera.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"abundera-api": {
"type": "http",
"url": "https://abundera.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: abundera-api
Remote MCP URL: https://abundera.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"abundera-api": {
"url": "https://abundera.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"abundera-api": {
"type": "http",
"url": "https://abundera.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "abundera-api",
"transport": "streamable-http",
"url": "https://abundera.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for abundera.ai was fetched 2026-08-26T02:01:53.058Z and is being refreshed.
abundera.ai is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.