Sypha AI Docs
Mcp

Adding MCP Servers from GitHub

This guide delivers step-by-step instructions for utilizing Sypha to construct an existing MCP server from a GitHub repository.

Finding an MCP Server

Multiple online sources exist for discovering MCP servers:

  • Sypha can automatically incorporate MCP servers into its list, which you can subsequently modify. Sypha directly clones GitHub repositories and constructs the servers for you.

  • GitHub: Two primary locations for discovering MCP servers on GitHub include:

  • Online directories: Various websites catalog MCP servers including:

    These directories enable users to organize servers by multiple criteria including downloads, date, stars, and use case. Each listing displays information such as features, tools, and configuration guidance.

  • PulseMCP: This platform features a blog post exploring how AI might utilize MCP servers to render websites obsolete. PulseMCP additionally includes an FAQ section addressing MCP servers: https://www.pulsemcp.com/

Building with Sypha

  1. Initiate the Process: Supply Sypha with the following details:

    • GitHub Repository URL: The repository's URL.
    • README.md Contents: This is optional yet beneficial for Sypha to comprehend the server's function and configuration. You can extract the README.md file from the GitHub repository.
  2. Example Interaction with Sypha:

    User: "Sypha, I want to add the MCP server for Brave browser control. Here's the GitHub link: @https://github.com/modelcontextprotocol/servers/tree/main/src/brave-search Can you add it?"
    
    Sypha: "OK. Cloning the repository to the MCP directory. It needs to be built because it has a 'package.json' file. Should I run 'npm run build'?"
    
    User: "Yes, build it."
    
    Sypha: "Build complete. This server needs a browser path. Where's your Brave browser executable?"
    
    User: "It's in '/Applications/Brave Browser.app/Contents/MacOS/Brave Browser'."
    
    Sypha: "OK. I've updated the server config with that path and added it to 'sypha_mcp_settings.json'. Anything else?"
    
    User: "No, that's all. Let's test it."
    
    Sypha: "Great! Starting the MCP Inspector to test the server connection. After that, we can try controlling the browser from Sypha."
  3. Sypha's Actions: Following your instructions, Sypha will execute the following:

    • Repository Cloning: Sypha clones the repository to your local machine, typically in the directory designated in your configuration.
    • Tweaking: You can direct Sypha to adjust the server's configuration. For example:
      • User: "This server requires an API key. Can you find where it should be added?"
      • Sypha may autonomously update the sypha_mcp_settings.json file or other pertinent files according to your instructions.
    • Building the Server: Sypha executes the suitable build command for the server, commonly npm run build.
    • Adding Server to Settings: Sypha incorporates the server's configuration into the sypha_mcp_settings.json file.

Testing and Troubleshooting

  1. Test the Server: Upon Sypha completing the build process, validate the server functions as anticipated. Sypha can provide assistance if you experience any issues.
  2. MCP Inspector: You can utilize the MCP Inspector to validate the server's connection and functionality.

Best Practices

  • Understand the Basics: While Sypha streamlines the process, possessing fundamental understanding of the server's code, the MCP protocol (learn more), and server configuration approaches enables more effective troubleshooting and customization.
  • Clear Instructions: Supply clear and precise instructions to Sypha throughout the procedure.
  • Testing: Comprehensively test the server following installation and configuration to verify proper functionality.
  • Version Control: Employ a version control system (like Git) to monitor changes to the server's code.
  • Stay Updated: Maintain your MCP servers current to leverage the latest features and security enhancements.

On this page