MCP Server List | Zyeon UI

Preview in your theme

status='ready' — six servers over three transports. The header only credits servers that are BOTH switched on and connected, so flipping sentry back on or disabling filesystem moves the 'tools available to the model' figure immediately. github is parked at needs-auth and postgres failed to spawn: both open themselves, because a row asking for a decision one click away from being seen is a row that gets missed. Toggling sentry on is rejected on purpose — watch the switch snap back with the reason underneath. Reconnecting postgres fails once, then succeeds.

2 of 6 servers connected · 17 tools available to the model

1 server failed1 server needs authorization

Transport
Streamable HTTP
Endpoint
https://api.githubcopilot.com/mcp/
Protocol
2025-06-18
Version
1.4.0
Capabilities
34 tools
Authorization
```
The server answered 401 and advertised an authorization server at https://github.com/login/oauth.
Your access token expired 2 days ago — authorize again to restore all 34 tools.
```
Tools · last known
- search_repositories
- get_file_contents
- create_or_update_file
- create_branch
- create_pull_request
- get_pull_request_diff
- merge_pull_request
- list_issues
22 more names not cached yet
Transport
stdio
Command
npx -y @modelcontextprotocol/server-postgres postgresql://localhost:5432/app
Protocol
2025-06-18
Version
0.6.2
Capabilities
3 tools
Last error
```
Process exited with code 1 after 240 ms.

  Error: connect ECONNREFUSED 127.0.0.1:5432
      at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16)

  DATABASE_URL points at a local Postgres that isn't running.
```
Tools · last known
- query
- list_schemas
- describe_table

no callback fired yet

status='ready', read-only (no callbacks passed, so no switches and no reconnect buttons are drawn — an affordance that does nothing is worse than none). These are the rows that break naive layouts: 34 cached tool names against a chip cap of 8, a 58-character server name, a spawn command far longer than the row is wide, a catalogue whose 19 names were never cached, and a server with 18 resources but zero tools.

3 of 4 servers connected · 53 tools available to the model

Transport
stdio
Command
npx -y kubernetes-mcp-server@latest --kubeconfig ~/.kube/config --context prod-eu-west-1
Protocol
2025-06-18
Version
0.14.0
Capabilities
34 tools · 12 resources · 2 prompts
Tools
- override_card
- override_array
- navigate_firewall
- hack_feed
- bypass_panel
- bypass_array
- synthesize_sensor
- bypass_program
Transport
stdio
Command
pnpm --filter @internal/platform-services exec node ./dist/mcp/entitlements-reconciliation-server.js --namespace platform.billing.entitlements --idempotency-window 86400
Protocol
2025-06-18
Version
3.11.0-rc.4
Capabilities
19 tools
Tools
19 tools reported · names weren't included in this response.
Transport
Streamable HTTP
Endpoint
https://wiki.example.com/mcp
Protocol
2025-06-18
Version
1.0.7
Capabilities
0 tools · 18 resources · 4 prompts
Tools
Connected, but this server exposes no tools.
Transport
stdio
Command
npx -y @modelcontextprotocol/server-puppeteer
Protocol
2025-06-18
Version
0.6.2
Capabilities
7 tools
Tools · last known
- navigate
- screenshot
- click
- fill
- select
- hover
- evaluate

status='loading' — the client config itself hasn't arrived. Rows are skeletons, not a spinner, so the list doesn't jump when it lands.

status='empty' — no servers configured yet. The add tile is the whole point of the state, so it is the CTA here.

No MCP servers configured

Connect a local stdio server or a remote Streamable HTTP endpoint, and its tools become available to the model.

onAddServer not fired yet

status='error' — the config couldn't be read at all. A different failure from a server failing to start, so it reads differently and offers a retry.

Couldn't load your MCP servers

We couldn't read your MCP client configuration.

onRetry not fired yet

Loading preview…

This component is part of Pro

The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.

Unlock with Pro

Process exited with code 1 after 240 ms. Error: connect ECONNREFUSED 127.0.0.1:5432 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1607:16) DATABASE_URL points at a local Postgres that isn't running.