Configuring Servers

Admins control which MCP servers and tools are available to the organization.

Adding a Server

Option 1: Marketplace

1. Click Browse Marketplace.
2. Select a server and click Add.

Option 2: Custom Server

1. Click Add Custom.
2. Manual: Enter the name, command (e.g., uvx, npx), and arguments.
3. JSON: Paste a configuration in VS Code or standard MCP format.

Template Variables

Use {VARIABLE_NAME} in arguments or environment variables. These can be configured globally by admins or individually by each user.

Server Management

Overview

View the server's command, status, and detected capabilities (tools, resources, prompts).

Status Toggles

• Enable/Disable: Turn servers on or off globally.
• Validate: Test the configuration. Edison Watch will attempt to start the server and discover its tools.
• Reinitialize: Restart all servers to apply configuration changes.

Tool Configuration

In the Tools tab, classify each tool:

• Enabled: Allow or block usage.
• Security Flags: Mark as Write Operation, Private Data, or Untrusted Data.
• ACL: Set the data sensitivity level.

Example Configurations

GitHub Integration

{
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://api.githubcopilot.com/mcp/",
    "--header",
    "Authorization: Bearer {GITHUB_TOKEN}"
  ]
}

PostgreSQL Database

{
  "command": "npx",
  "args": [
    "-y",
    "@modelcontextprotocol/server-postgres",
    "postgresql://localhost/mydb"
  ]
}

Zapier Automations

{
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://mcp.zapier.com/api/mcp/s/{ZAPIER_ACCESS_TOKEN}/mcp"
  ]
}

Local Filesystem

{
  "command": "uvx",
  "args": ["mcp-server-filesystem", "/path/to/dir"]
}