Model Context Protocol

Give your agents the use case corpus as tools.

The same curated, source-linked deployments behind AIUseCaseHub are exposed as a remote MCP server. Point any MCP-capable client at the endpoint below and your agent can search and retrieve cases without you writing a single HTTP call.

Get an API keyFull endpoint reference
Tools

4

exposed to agents

Typical cost

2

credits per search call

Connection

Connect a client

Authentication is key based. Send your personal API key in the X-API-Key header — the same key used for the REST API. In Microsoft Foundry, choose key-based authentication and enter X-API-Key as the credential name.

Foundry MCP connection
Remote MCP Server endpoint:
https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp

Authentication:
Key-based

Credential:
X-API-Key: <YOUR_API_KEY>
Generic MCP client config
{
  "mcpServers": {
    "aiusecasehub": {
      "url": "https://basic-backend713-dsd8hygyfkc8d8f5.swedencentral-01.azurewebsites.net/api/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Keys are created and rotated on the REST API page. A key is only shown once, right after it is generated.

Tool catalog

Available MCP tools

Search tools return ranked case summaries; the detail tool resolves a single record by its row key.

search_usecases
Hybrid search2 credits

Default agent search tool. Preserves the existing search_term contract while using hybrid full-text plus vector ranking behind the scenes.

Arguments: search_term, limit

hybrid_search_usecases
Hybrid search2 credits

Explicit hybrid search tool for agents that want natural-language query semantics and combined ranking scores.

Arguments: query, limit

vector_search_usecases
Vector search2 credits

Semantic-only tool for similarity search when keyword matching is not needed.

Arguments: query, limit

get_usecase_details
Detail lookup1 credits

Fetch the detailed record for a specific use case returned by a search tool.

Arguments: row_key

Good to know

Credits and limits

  • MCP tool calls draw from the same monthly credit balance as REST calls. Search tools cost 2 credits, detail lookups cost 1.
  • Browsing the site in the app does not consume credits — only external API and MCP calls do.
  • Prefer search_usecases for general agent search; it uses hybrid ranking while keeping a stable argument contract.
  • Chain a search tool with get_usecase_details to keep responses small and only expand the cases the agent actually needs.