MCP servers: local, network and bot-added
Add an MCP server that runs on this computer or your own network, turn on a server a bot saved for you, and paste a link, a command or a JSON snippet in a form Murage reads.
Servers on this computer or your network
A link that points at this computer, or at a device on your local network, asks you to confirm before Murage connects. That is on purpose. A server on your own machine can run programs there, and a box on your home network could be anything from a NAS to a Raspberry Pi somebody else set up. Murage checks the address again on every connection, so you see the question each time the address changes, and never when it has not.
You see
This link points to this computer. Only continue if you started this server yourself.Do this
You started it, say with npx or a Docker command in a terminal? Choose Continue. You did not, or you are not sure what is listening on that port? Choose Go back and find out first.
You see
This link points to a device on your local network. Only continue if you know what runs there.Do this
Murage shows the device's address in the message. Choose Continue when you know the machine and the service on it. A home server you run, or a colleague's test box on the office network, is fine. An address you do not recognise is not.
After you continue, the server is saved switched off like any other. Choose Test to see its tools, then Turn on.
A server your bot saved for you
Ask a bot for a tool it does not have and it can save the server for you. The bot never turns it on. It lands in Connected appsMCP servers switched off, and any key the server needs goes on a card of its own, which the bot never sees.
A bot also never writes an mcp-remote or npx command for you to run. If a service gives you a link, the bot tells you to open Connected apps, then MCP servers, and paste the link there. Murage handles the sign-in.
Step 1
Ask the bot
Say what you want, for example "add the Linear MCP server so you can read my issues". If the bot knows the server, it saves it and tells you where to find it.
You're done when: the bot says it has saved a server for you.
Step 2
Open the server
Open Connected appsMCP servers. The new server is at the bottom of the list.
You're done when: you see the new server in the list, switched off.
Step 3
Check it and turn it on
Read what it is and where it points. Choose Test to see the tools it offers. If it asks for a key, paste it on the card. Then choose Turn on. Bots can use the tools from their next task.
You're done when: the server is on.
What you can paste
Add server takes three shapes: a link, one command, or a JSON snippet. Murage works out which you pasted. It does not take a Codex config.toml or a YAML file, so when a service hands you one of those, pick out the server's link or its command and paste that instead.
A command has to be a single command. Murage runs it directly rather than through a shell, so a pipe, a redirect or a $(...) substitution is refused. npx -y some-server --port 3000 is one command. cat key.txt | some-server is not.
A JSON snippet can hold up to 20 servers and up to 64 KiB. If you have a bigger config, paste it in parts.
You see
Codex config.toml files are not supported yet. Paste the server's link or its command instead.Do this
Open the .toml file, find the server you want, and paste its url or its command with its args as one line.
You see
YAML config is not supported. Paste the server's link, its command, or a JSON snippet instead.Do this
Same fix. Take the link or the command out of the YAML and paste that.
You see
That is more than 64 KiB. Paste just the part for the server you want.Do this
A whole config file from another app is too big. Paste one server's block at a time.
You see
That snippet has more than 20 servers. Paste fewer at a time.Do this
Split the snippet. 20 servers per paste.
You see
That looks like JSON but could not be read. Check for a missing bracket or quote.Do this
Usually a trailing comma or a quote that got lost in copying. Paste it into a text editor, fix it, paste again.
You see
None of the servers in that snippet has a command or a link.Do this
Every server entry needs either a command or a url. A snippet with only names and environment variables gives Murage nothing to start.
Good to know
- Desktop only. Adding and changing servers happens in the desktop app. Murage Cloud (coming soon) changes this later.
- Saved off. Every server, whoever added it, starts switched off until you choose Turn on.
- Which engines. Your own servers reach bots on Fuigo, Claude Code, Codex and the other engines that take MCP servers. See the engines table.
- Checked every time. A local or network address asks again whenever it changes.