Uk Petitions MCP server
{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-petitions/"
}
}
}{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-petitions/"
}
}
}{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-petitions/"
}
}
}{
"servers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-petitions/"
}
}
}{
"mcpServers": {
"mcpbundles-hub": {
"type": "http",
"url": "https://mcp.mcpbundles.com/bundle/uk-petitions/"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
This is a bundle aggregator MCP server that provides access to tools from all enabled MCPBundles. It connects AI assistants to over 1,500 provider integrations like GitHub, Slack, Notion, and Stripe through a unified interface.
- Execute tools from multiple bundled providers using a single MCP endpoint authenticated with OAuth or API key.
- Search and discover available tools across all enabled bundles to understand what integrations are ready to use.
- Check bundle configuration status and credential readiness before running tools.
Tools this server exposes
| Tool | Does |
|---|---|
| execute_tool | Run any tool from your enabled bundles with automatic credential handling. |
| list_tools | Discover all tools available across your enabled bundles. |
| search_tools | Find tools by name, provider, or capability. |
| check_readiness | Verify bundle configuration and credential status. |
| get_tool_details | View parameters, descriptions, and usage information for a specific tool. |
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.