One Place to Manage Your MCP Servers

No fake green lights. No credential circus.

MCP Hub command bunker with a glowing red MCP core and connected server controls

MCP Hub is an early-access, mobile-first workspace for connecting HTTPS Model Context Protocol servers, inspecting their tools, and testing integrations. We are building the secure plumbing first, because pretending an unfinished automation platform is a product is how trust gets murdered.

What You Actually Get

Secure connection foundation

HTTPS-only server registration, outbound request controls, tenant boundaries, and encrypted credential storage are the work in progress—not vaporware bullet points.

Server connection workflow

Name an HTTPS MCP endpoint, choose a supported authentication method, test the connection, and see its honest status in one place.

Tool discovery and execution

The app includes the foundation for inspecting server tools and sending tool calls. Broader automation orchestration remains deliberately gated until its durable security model exists.

Clear operational signals

Connection status, test results, and execution records are designed to answer the useful question: did the server work, or did it fall on its face?

Mobile-first onboarding

An eight-step product tour and replayable onboarding guide help new users understand the workspace before we ask them to trust it with anything important.

Early access, honestly labeled

OAuth callbacks, webhooks, and workflow scheduling are not being marketed as ready. They stay unavailable until tenant-scoped persistence and review land.

How It Works

1

Add an HTTPS endpoint

Enter a connection name, a standard-port HTTPS endpoint, and only the authentication method the server actually requires.

2

Test the connection

MCP Hub validates the endpoint through its outbound policy, tests the connection, and reports the result instead of manufacturing a success badge.

3

Discover and call tools

Explore tools provided by the connected server and run targeted calls through a tenant-scoped runtime.

4

Grow only when the foundation holds

Scheduled workflows, webhooks, and OAuth automation come later—after their durable lifecycle models can be built without handing security a loaded gun.

Product Previews

These interactive pages are visual previews of product directions, not live connected-server promises.

⚡ Workflow Builder

Preview a possible visual workflow-building direction.

⚙️ Live Execution

Preview how a future execution view could communicate state.

🎯 Features

Preview the product surface without inventing operational guarantees.

What We Will Not Fake

No imaginary uptime: We will not quote reliability targets without production evidence.

No pretend integrations: A provider card is not a live integration unless the secure end-to-end flow exists and is testable.

No fake enterprise theater: We will not promise compliance, team controls, disaster recovery, or on-premise deployment until the product can actually support those claims.

If that makes the page less shiny, good. It makes it more useful.

Current Foundation

React Native 0.81
Node.js + Express
MySQL + Drizzle
Expo Router
NativeWind
AsyncStorage
TypeScript 5.9
tRPC
HTTPS outbound policy
AES-256-GCM
Vitest

Early Access

Join the list

Beta
availability is limited
  • Tell us which MCP server you need
  • Tell us the job it should do
  • Receive access updates by email
Request early access

Feedback channel

Useful
tell us what hurts
  • Connection flow feedback
  • Security requirements
  • Workflow use cases
Send feedback

Want In Before It Gets Polished to Death?

Request early access, tell us the MCP server you need to manage, and help shape the part that should exist before the marketing department starts hallucinating outcomes.

Request early access