MCP Servers

MCP Servers 🔌

From me, for you · Last reviewed: 2026-09-17

MCP (Model Context Protocol) lets me use tools provided by other services. What I can do depends on the server you connect: it might search reference material, read documents, or change something in another app.

Add and manage servers in Lumiverse → Settings → MCP Servers. I use those same profiles through chat. There's no separate MCP management screen inside LumiAgent.

Set up a server

1. Use Lumiverse 1.2.0 or later and update LumiAgent. If you also use LumiRealm, update it for the bridge permission fixes.
2. Open Extensions → LumiAgent and grant mcp_servers and mcp_servers.create. The first lets me discover, connect to, and use servers. The second lets me create profiles when asked.
3. Open Settings → MCP Servers → Add MCP Server. Give it a name, choose the transport from the server's instructions, and enter its connection details.
4. Save the profile with Enabled on. Connect it there, or ask me to connect. Auto-connect controls whether Lumiverse connects it at startup.

Transport	What to enter
Streamable HTTP	The server's HTTP(S) MCP endpoint and any required headers.
SSE (Legacy)	The server's SSE endpoint and any required headers.
Stdio (Subprocess)	An executable, comma-separated arguments, and any environment variables. The command runs on the machine hosting Lumiverse.

Lumiverse's network and executable policies still apply. A stdio server needs its executable installed on the host, and its launch must be allowed there.

Enter credentials in Lumiverse's settings to keep them out of our conversation. Profile discovery hides stored credential values from me, but anything you type into chat or ask me to pass as a tool argument remains in the conversation.

Ask me to use it

You can leave All Characters selected. A focused character or pinned chat isn't required for MCP.

• "Show me my MCP servers and which ones are connected."
• "Connect to my reference server and show me what its tools can do."
• "Use my reference server to find material about this setting, then draft lorebook entries from it."

I'll find the server, connect if needed, inspect the tools it advertises, and call the ones that fit your task. Searches and other actions in these examples depend on what that server provides.

You can also ask me to create a profile from an endpoint or command you supply. Profiles I create default to Auto-connect off, and creation doesn't connect immediately. Edit, disable, disconnect, or delete profiles through Lumiverse's MCP settings.

Approval and undo

When change approval is enabled, creating a profile, connecting a server, and calling a remote tool go through that approval flow. Browsing profiles, checking status, and listing tools don't request change approval.

MCP profile creation and remote changes aren't recorded in the Workshop edit history and can't be reverted there. If a call times out or reports an error, check the remote service before repeating a change: the operation may already have happened.

If something doesn't work

Symptom	What to check
No servers found	Add one in Lumiverse's MCP settings under the same user account you're using with LumiAgent.
Server isn't connected	Enable and connect the profile. Listing or calling its tools doesn't connect it automatically.
Connection failed	Open the profile in Lumiverse's MCP settings for details. Check the endpoint or command, credentials, and host policies.
MCP permission missing	Grant the named permission to LumiAgent in Extensions. If its missing-permissions dialog asks you to toggle it off and on, do that after granting.
LumiRealm bridge warning	Update both extensions. LumiRealm needs no MCP grants for this bridge. If a real missing permission such as characters is named, grant it to the extension identified by the banner.
A returned image or audio clip isn't visible to me	MCP results currently arrive as text or serialized data. Media blocks aren't automatically passed to my model as images or audio.

The LumiRealm bridge uses a separate phone line. Its request and probe channels require characters, so granting MCP access to LumiAgent doesn't add an MCP requirement to LumiRealm. Genuine bridge permission failures still produce a warning.

See also

Tools and Capabilities · Agent Settings · Workshop · Phone Line