> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mira-app.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Session vs Global MCP Servers

> Choose the right scope for each MCP server — active only in one chat, or always available.

Every MCP server added to MIRA has a **scope** that controls when its tools are injected into the engine's context.

## Scopes at a glance

|                                | Session                          | Global                                            |
| ------------------------------ | -------------------------------- | ------------------------------------------------- |
| **Available in**               | Current chat only                | All chats                                         |
| **Set at**                     | Add/edit time                    | Add/edit time                                     |
| **Persists after chat closes** | No                               | Yes                                               |
| **Overridable per session**    | N/A                              | Yes — can be disabled for one session             |
| **Use case**                   | Task-specific or untrusted tools | Always-on utilities (e.g. filesystem, web search) |

## Setting scope

When adding or editing a server, choose **Session** or **Global** from the **Scope** dropdown. You can change scope at any time in Settings → MCP Tools.

## Global servers

Global servers start when MIRA launches and remain connected throughout all sessions. Their tools are always present in the engine context unless explicitly disabled for a specific session.

**Best practices for global servers:**

* Use only for tools you want available in every conversation.
* Prefer read-only tools (filesystem reads, web search) over write tools for global scope.
* Audit global server tool lists periodically — a large global toolset increases context token usage.

## Session servers

Session servers connect when activated and disconnect when the chat session ends or when you switch to a different chat.

To activate a session server:

1. Open a chat session.
2. Click the **MCP** icon in the toolbar.
3. Toggle the server on.

## Disabling a global server for a session

Even with a global server configured, you can exclude it from a specific session:

1. Open the session.
2. Click the **MCP** icon.
3. Toggle the global server off for this session.

The server remains global for all other sessions.

## Security model

MIRA asks for confirmation the first time an engine calls a tool from a newly added server. You can choose:

* **Allow once** — approve the call for this invocation only
* **Allow for session** — approve all calls from this server in the current session
* **Always allow** — skip confirmation for this server in all sessions

<Warning>
  "Always allow" should only be set for servers you fully trust. A misbehaving server could invoke destructive tools without further prompts.
</Warning>

<Note>Edit this page — [Open a pull request](https://github.com/satyendra2013/mira-app/edit/main/docs/features/mcp-tools/session-vs-global.mdx)</Note>