> 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/stackai-mcp/tool-reference/projects-and-workflow-authoring/projects-get.md).

# projects\_get

Read project metadata, UI/input configuration and a paginated graph. The default `version: "published"` falls back to the draft when no published version exists. Inspect `source_version`.

**Effect:** This call reads data and does not run or change a project.

## Inputs

| Name         | Type                   | Requirement | Description                                                                                                          |
| ------------ | ---------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------- |
| `project_id` | string                 | Required    | ID returned by `projects_list`; use a project in the active organization.                                            |
| `version`    | `published` or `draft` | Optional    | `published` (default, with draft fallback) or `draft`.                                                               |
| `cursor`     | string                 | Optional    | Opaque `pagination.next_cursor` from the preceding page. Omit for the first page; preserve the resource and filters. |
| `page_size`  | integer                | Optional    | Results per page. Default 50; maximum 200. Minimum 1.                                                                |
| `verbose`    | boolean                | Optional    | Default `false`. Include expanded details. See behavior below for the scope of expansion.                            |

## Example

These are MCP tool arguments, not an HTTP request body. Replace bracketed IDs with values returned from your account.

```json
{
  "project_id": "<project-id>",
  "version": "draft"
}
```

## Result

Abbreviated result example; unshown fields are omitted for clarity.

```json
{
  "flow_id": "<project-id>",
  "source_version": "draft",
  "found": true,
  "nodes_count": 3,
  "edges_count": 2,
  "pagination": {
    "has_more": false,
    "next_cursor": null
  }
}
```

## Behavior

Use version="draft" before editing.

Each page includes its nodes and their connecting edges. Some edges connect to nodes on another page, identified by `referenced_node_ids`. Deduplicate edges by ID when combining pages. verbose=true includes the raw flow only below the server size cap.

## Troubleshooting

If `flow_too_large` is returned, omit `verbose` and follow graph pagination. If `source_version` is `draft`, do not assume a published version exists.

## Related resources

[Projects and workflow authoring](https://docs.stackai.com/stackai-mcp/tool-reference/projects-and-workflow-authoring.md)

[Inspect and run a published project](https://docs.stackai.com/stackai-mcp/workflow-recipes/inspect-and-run-a-published-project.md)

[Edit, validate and publish deliberately](https://docs.stackai.com/stackai-mcp/workflow-recipes/edit-validate-and-publish-deliberately.md)

[Connection, permissions, pagination, and recovery](https://docs.stackai.com/stackai-mcp/best-practices-and-troubleshooting.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/stackai-mcp/tool-reference/projects-and-workflow-authoring/projects-get.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.
