EvergreenDocs

Add your own server

Add an MCP server that isn't in the Integrations list, choose who can use it, and block any tools you don't want the agent to have.

  • Owner · Admin

If a tool you use isn’t in the Integrations list, an Owner or Admin can add its MCP server. The server becomes a private listing. Only your workspace sees it, and it works like any other integration from then on.

Before you begin

  • You’re an Owner or Admin of your Evergreen workspace.
  • You have the server’s https:// address. Evergreen connects to servers over https:// only, so it can’t use a server that runs as a local command.
  • If the server signs people in with its own OAuth app, you have that app’s client ID and client secret, or can create them with the vendor.

Add the server

  1. Start the add

    Open Workspace settings › Integrations and choose the + button beside Settings, which is named Add your own server.

    There’s a shortcut. Paste the server’s address, or an mcpServers entry, into the list’s search box. A row appears that reads Add followed by the server’s host, then as private to and your workspace’s name. Choose it to add the server and open the guided install straight away.

  2. Paste the server

    The dialog is called Add provider. In Server URL or definition, enter the server’s https:// address, or paste an mcpServers block, a server.json file, or an Evergreen definition. Under Try one: are examples of each. Choose Continue, and Evergreen reads the server.

  3. Check what Evergreen found

    Evergreen shows the server’s name, which you can rename by clicking it, and its host. It also shows how many tools the server lists, split into read and write. If the server lists none yet, it says so. Many servers list their tools only after someone signs in.

  4. Say how people sign in

    Evergreen tells you which of these ways the server uses.

    The server says What it means What you give
    Registers automatically The server signs people in with OAuth and lets Evergreen register itself. Nothing.
    Your own OAuth client The server signs people in with OAuth but doesn’t let Evergreen register itself. Create an app with the vendor, give it the Redirect URI to give the vendor that Evergreen shows, then paste the Client id and Client secret.
    No sign-in, shared key The server has no sign-in. If it needs a key, every call uses the same shared key, so calls aren’t attributed to a person. If the server needs a key, enter a Header name and its Value. Leave the value empty and no header is sent.
    Each person’s own key The server takes a key each person makes on the provider’s own page, so every call is theirs. Evergreen finds this in a pasted Evergreen definition that says so. Nothing. Each person pastes their own key when they connect.

  5. Add more detail if you want

    Choose More options to set a Description, which reads “What the agent can do with it” as a hint, a Category, the Sign-in method if Evergreen guessed wrong, and Guidance for the agent. A server that takes each person’s own key has no Sign-in choice. Guidance is text for your own table names, roles, and conventions, and the agent gets it with the server’s instructions in each session.

  6. Add it

    Choose Add provider. The server starts off, and nobody can use it until you choose who can.

Evergreen refuses an address that doesn’t start with https://, and it says so in words. A pasted entry that runs a local command, has no url, or isn’t valid JSON is refused too.

Choose who can use it

A new server is added off and available to nobody. After you add it, Manage opens on Who can use it. Pick Everyone or Selected audiences, and anyone left out sees a Request button. You manage audiences in Workspace settings › Features.

The first audience you save also turns the server on, as long as nothing else is left to set up. A server with a shared key, or one that takes each person’s own key, turns on straight away. For a server people sign in to, you sign in first. The tab says the server turns on once you finish the Sign in step and keeps who you chose. Choose Finish setup on the server’s row to sign in, and the server turns on.

If you added the server by pasting into the search box, the guided install opens instead. Its first step, Check who runs it, reminds you that Evergreen sends your people’s sign-ins and requests to this server, so make sure you trust whoever runs it. The steps that follow are Sign in, Who can use it, and Done. When you choose Turn on for your workspace, the server is on.

How people connect

Each person opens Settings › Integrations, finds the server, and chooses Connect. They sign in the way the server uses. For a server that takes each person’s own key, the button reads Add key. Get a key opens the page where they make one, and they paste it into the dialog. A person who can’t connect yet sees Request or Request access, and the request comes to you.

Members can also ask for a server that isn’t in the list. They choose Request an MCP on Settings › Integrations and paste the server’s address. You see it under the Requests status filter as an Unknown server. Choose Review and install and the Add provider dialog opens with the address filled in. Adding the server approves the request and tells the requester.

Block tools

Open Manage on the server and go to the Tools tab. It lists what the server offers, each marked read or write, with a switch to block any tool. The agent can use read tools while it plans, and write tools once the plan is approved. A blocked tool isn’t offered to the agent in anyone’s session.

The list fills in after someone connects and uses the server in a session. Until then it says No tools are listed yet.

Remove it

Choose Remove at the bottom of the Overview tab in Manage. It signs out everyone who’s connected, deletes your workspace’s settings for the server, and deletes the listing itself. In the list’s menu for the row, the same action reads Delete. While anyone is connected, you type the server’s name to confirm. To add the server again, you start over from its address or definition.

Note

Evergreen sends your people’s sign-ins and requests to the server you add, so only add servers you trust.

Limits

  • Evergreen connects to servers by https:// address only.
  • Your private listings are visible to your workspace alone.
  • A server with no sign-in uses one shared key for everyone, so its calls aren’t attributed to a person.
  • A server that takes each person’s own key needs an Evergreen definition that says so. An address alone is read as one of the other ways.

Troubleshooting

What you see What to do
Use the server’s https:// address Enter an address that starts with https://.
That server runs as a local command Evergreen can’t use a server that starts on a laptop. Use its hosted https:// address.
That entry names no server with a url Paste the whole mcpServers entry, including the server’s url.
Give the provider a name to add it Click the server’s name in the dialog and type one.
Another provider already uses the key Rename the provider, and Evergreen picks a different key.
No tools are listed yet The server lists its tools after someone signs in. Connect, use it in a session, and the list fills in.
People don’t see the server It starts off and open to nobody. Choose who can use it. If it signs people in, choose Finish setup and sign in so it turns on.
The server was added but its secret wasn’t stored Enter the client secret or header value again on the server’s Overview tab in Manage.

Last updated

Esc