Multi-tenant MCP Server

Created By
brianintegrationappa year ago
Multi-tenant service that allows MCP Clients to connect to Integration App's MCP Server
Overview

What is MCP Service?

MCP Service is a multi-tenant Model Context Protocol (MCP) server that allows multiple tenants to connect to an Integration App's MCP server using their own credentials.

How to use MCP Service?

To use MCP Service, set up the environment variables, install dependencies, and start the server. You can then create tenants and interact with the API endpoints for managing integrations and tools.

Key features of MCP Service?

  • Multi-tenant support with isolated connections
  • Database persistence for tenant information
  • Live tool discovery from Integration App
  • Audit logging and security middleware
  • Health check endpoint
  • Rate limiting and graceful shutdown handling

Use cases of MCP Service?

  1. Managing multiple tenant integrations in a single application.
  2. Providing isolated environments for different clients.
  3. Facilitating secure API interactions for various tools and services.

FAQ from MCP Service?

  • How do I create a tenant?

You can create a tenant by sending a POST request to /api/tenants with the required admin token and tenant details.

  • What are the prerequisites for using MCP Service?

You need Node.js >= 18.0.0, a PostgreSQL database, and an Integration App account.

  • Is there a health check endpoint?

Yes, you can check the server status using the /health endpoint.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
brianintegrationapp
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

6 hours ago