> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/apis-and-mcp/mcp-mutation-and-version-selection-behavior.md).

# MCP Mutation and Version-Selection Behavior

MCP tools can read resources, run workflows, or change configuration. Review the selected operation and version before a call that changes data.

![Inspect the published project explicitly](https://1957915746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2F2TXKYZkcO8sEnel61wDV%2Fmcp-mutation-and-version-selection-behavior.png?alt=media)

Example request within an initialized MCP session. projects\_get reads configuration; it does not execute the project. Version fields differ between tools—check the discovered schema.

<details>

<summary>Copy the example</summary>

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "projects_get",
    "arguments": {
      "project_id": "<project-id>",
      "version": "published"
    }
  }
}
```

</details>

## Before you begin

An authenticated MCP client with the required tool and resource permissions.

## Key concepts

| Term              | Definition                                                                                                                                                                |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Read-only mode    | A server configuration that limits available operations to supported non-mutating capabilities. Discover the actual tool set; execution and mutation tools can be absent. |
| Project version   | A specific saved configuration of a project. Select it explicitly when a result must be reproducible.                                                                     |
| Side effect       | A change outside the returned answer, such as creating a record or sending email. Cancellation or release rollback does not undo a completed side effect.                 |
| Revision conflict | A response indicating that the resource changed since the version used for an edit. Read current state and reconcile changes before resubmitting.                         |

## Configuration options

| Option  | Purpose                                                                            | Behavior                                                                      |
| ------- | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Dry run | A supported preview or validation option that avoids applying the selected change. | Its scope belongs to the specific operation; it is not a universal parameter. |

## Select a version for an MCP operation

1. Read the tool’s schema and select the intended organization and project.
2. Set its supported version and publication options explicitly where needed.
3. Inspect the returned result and read the resource again after a change.

The tool performs the intended operation against the intended resource version.

## Behavior and limitations

Read-only configurations can omit mutation and execution tools. A dry-run option applies only where the specific tool supports it. A project run and a project edit are different operations. Use the selected tool’s version contract rather than assuming REST selector values apply unchanged.

## Related resources

[API Versions and Compatibility](https://docs.stackai.com/technical-reference/apis-and-mcp/api-versions-and-compatibility.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/apis-and-mcp/mcp-mutation-and-version-selection-behavior.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
