Skip to content

Conversation

@domdomegg
Copy link
Member

Description

New server submission.

Server Details

  • Server: 1mcpserver
  • Changes to: Added server

1mcpserver is a MCP server agent of MCP servers. Automatic discover, configure, and add MCP servers on your local machine.

Our MCP server is available at https://mcp.1mcpserver.com/mcp/ or can also be set up locally using STDIO. See more at https://github.com/particlefuture/1mcpserver

Motivation and Context

Right now, most MCP server search are done via github searching or online google search. There has been several MCP wrappers, but most serves as an middleware infrastructure that hosts different MCP at an endpoint. The gathering of which MCP to host is still mostly done by manual search. We provide an automatic pipeline of not only searching but also automatically configuring MCP servers.

How Has This Been Tested?

Tested with Claude and Cursor with both remote endpoint and local stdio for 10 times with web-analyzer example. See quickstart_demo.md in our repo for more details.

Breaking Changes

Update mcp config file with:

    "mcp-server-discovery": {
      "url": "https://mcp.1mcpserver.com/mcp/",
      "headers": {
        "Accept": "text/event-stream",
        "Cache-Control": "no-cache",
        "API_KEY": "value"
      }
    }

⬆️we are using the name mcp-server-discovery here because it works better for LLMs.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Protocol Documentation
  • My changes follows MCP security best practices
  • I have updated the server's README accordingly
  • I have tested this with an LLM client
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have documented all environment variables and configuration options

Additional context

Robert-Jia00129 and others added 3 commits August 10, 2025 15:24
Move 1mcpserver from Official Integrations to Community Servers section
and update formatting to match community server style (remove logo image).

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
@domdomegg domdomegg merged commit fa9c4c0 into main Aug 17, 2025
12 checks passed
@domdomegg domdomegg deleted the Robert-Jia00129/main branch August 17, 2025 16:04
@Robert-Jia00129
Copy link
Contributor

Thanks. I'm hired by Particle Future to develop this MCP Server for them. What do I need to put this as official mcp servers?

@domdomegg
Copy link
Member Author

Hey @Robert-Jia00129, for us the definition of an official server is one that is "maintained by companies building production ready MCP servers for their platforms". Implicitly we also expect some surrounding evidence of a well-maintained and broadly-used platform/product backing it.

E.g. if Particle Future offered some well-used platform, and this MCP was used to access that platform, it would count.

I might be wrong here, but my understanding is that this MCP server is itself the product to access other platforms, rather than accessing its own platform? And the available documentation/community around Particle Future/1mcpserver is fairly sparse/small.

@Robert-Jia00129
Copy link
Contributor

I see. That's correct, it's not used to access any of our platforms built yet. Thanks for the clarification!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants