MCP Hub and Integrations
108 connectable apps, verified against their real servers.
The MCP Hub is one place to connect an account and hand its tools to the agent. A single MCP Connect button lists every connectable app in the order of what it asks of you -- apps that sign in through a browser first, then apps that want an API key, then apps that need nothing at all. Clicking one opens that app’s own consent page in your real browser, and once you allow it the tools are live in the session.
What is in the catalog
| Kind | Apps | What it means |
|---|---|---|
| Browser sign-in | 69 | Opens that app’s consent page. The token is stored on this machine. |
| Needs a token | 9 | You paste a token you created yourself. |
| Open | 19 | No sign-in. Public data, live immediately. |
| Runs locally | 11 | A process on this machine. Nothing leaves the box. |
initialize, then a tools/list, and where a read-only tool existed, an actual tools/call. Where a vendor has no usable MCP endpoint, the app is absent rather than present and broken.Categories
The 108 apps span 27 categories: AI & Media, Automation, Code, Commerce, Communication, Database, Design, Developer, Documents, Finance, Hosting, Infrastructure, Knowledge, Maps, Marketing, Media, Monitoring, Payments, Productivity, Project, Sales, Search, Social, Storage, System, Weather and more.
How authentication is classified
| Auth kind | Tier shown | What happens |
|---|---|---|
| oauth | Browser sign-in | A sign-in document is discovered, or the vendor issues a client from its console. Press Connect, allow, done. |
| token | Needs a token | No way in without a secret -- the handshake or the call demands a key. Paste it and it is connected. |
| none | No sign-in | Initialize, tools/list and a read-only call all answered with no credential at all. |
| local | Runs locally | Started as a local process on this machine. |
Bundled local servers
Four local MCP servers ship with the app, so nothing needs installing before the agent can act: Jarvis Browser, Nuphus, Touchpoint and desktop-commander. The Hub also runs servers fetched from a package registry on demand, reading only the environment variables each one declares.