Untapped

Provides an MCP bridge to Untapped data for Claude, enabling authenticated requests via a local MCP endpoint.

javascript

0

GitHub Stars

javascript

Language

4 months ago

First Indexed

3 weeks ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "etoxin-untapped-mcp": {
      "command": "node",
      "args": [
        "/Users/user/projects/untapped-mcp/build/index.js"
      ],
      "env": {
        "UNTAPPED_API_CLIENT_ID": "<YOUR_CLIENT_ID>",
        "UNTAPPED_API_CLIENT_SECRET": "<YOUR_CLIENT_SECRET>"
      }
    }
  }
}

You run an Untapped MCP server to integrate with Claude, enabling you to connect Claude-based workflows to Untapped data through a dedicated MCP endpoint. This server acts as a bridge, handling authentication and requests so your client can interact with Untapped APIs via the MCP protocol.

How to use

Start by configuring your MCP client to connect to the Untappd MCP server. You will run the server locally and point your client to the local process, supplying your API credentials so Claude can authenticate with Untapped.

How to install

Prerequisites: You need Node.js installed on your system. If you don’t have it yet, install Node.js from https://nodejs.org. You also need npm, which comes bundled with Node.js.

Clone the MCP server repository to your development machine, install dependencies, and build the project.

# Clone the Untapped MCP server repo
git clone https://github.com/etoxin/untapped-mcp.git
cd untapped-mcp

# Install dependencies
npm install

# Build the project (if a build step exists in the repo)
npm run build

# Start the server (example command shown in usage configuration)
node build/index.js

Additional sections

Configuration notes:

The server is designed to run as a local process and be referenced by your Claude Desktop configuration. You provide the necessary API credentials as environment variables when launching the server.

Security notes:

Treat your API client credentials as secrets. Do not commit them to version control and only load them from secure environment sources when starting the server.

Example startup and configuration (as shown by the usage example):

Start the server with Node using the built index: node build/index.js
Provide credentials via environment variables before starting: UNTAPPED_API_CLIENT_ID=your_client_id UNTAPPED_API_CLIENT_SECRET=your_client_secret node build/index.js

Configuration example for Claude Desktop

{
  "mcpServers": {
    "Untappd": {
      "command": "node",
      "args": ["/Users/user/projects/untapped-mcp/build/index.js"],
      "env": {
        "UNTAPPED_API_CLIENT_ID": "<YOUR_CLIENT_ID>",
        "UNTAPPED_API_CLIENT_SECRET": "<YOUR_CLIENT_SECRET>"
      }
    }
  }
}