Untappd MCP Server using Azure Functions
LocalAbout Untappd MCP Server using Azure Functions
An F# Untappd MCP server implemented as an Azure Function, using Server-Sent Events. It is intended as an example for connecting Untappd to MCP clients.
Key features
- 01Azure Functions implementation
- 02Server-Sent Events transport
- 03F# and .NET project
Use cases
- 01Expose an Untappd integration to MCP clients
- 02Run an MCP endpoint with Azure Functions
MCP support
It exposes an Untappd MCP server over Server-Sent Events. The README shows Claude Desktop connecting through mcp-remote because it does not support SSE configuration directly.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEUntappd MCP Server using Azure Functions
A version of the Untappd MCP Server using Azure Functions and Server Sent Events.
Blog post coming soon.
Configure Claude Desktop
Since Claude Desktop does not currently support SSE configuration you need to include a middle man component to make the calls to the SSE server.
Edit your claude_desktop_config.json:
{
"mcpServers": {
"untappddotnet": {
"command": "npx",
"args": [
"mcp-remote",
"http://localhost:7071/runtime/webhooks/mcp/sse"
]
}
}
}
Building
Prerequisites:
- dotnet 9.0
- Docker Desktop
local.settings.json Setup
{
"IsEncrypted": false,
"Values": {
"AzureWebJobsStorage": "<CONNECTION_STRING>",
"FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated",
"Untappd:ClientId": "",
"Untappd:ClientSecret": ""
}
}
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.