Uk Constituencies MCP server
{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-constituencies/"
}
}
}{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-constituencies/"
}
}
}{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-constituencies/"
}
}
}{
"servers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-constituencies/"
}
}
}{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-constituencies/"
}
}
}What it does
This is the MCPBundles Hub MCP server, a proxy that aggregates access to tools from across 1500+ provider integrations including GitHub, Slack, Notion, Google Drive, and others. It is for developers using Claude, Cursor, or other MCP-compatible assistants who want to connect multiple services through a single authenticated endpoint.
- Execute tools from multiple cloud services (GitHub, Slack, Google Drive) through one MCP server without configuring each individually.
- Search and discover available tools across enabled bundles to find what capabilities are available.
- Run authenticated operations like creating issues, sending messages, or managing files with credentials automatically handled by bundles.
Tools this server exposes
| Tool | Does |
|---|---|
| list_tools | Discover all tools available across your enabled bundles. |
| search_tools | Find tools by name, provider, or capability. |
| execute_tool | Run any tool from your enabled bundles with automatic credential handling. |
| get_tool_details | View parameters, descriptions, and usage information for a specific tool. |
| check_readiness | Verify bundle configuration and credential status before executing tools. |
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.