# RevCent MCP Guide: `GetProjectNote`

AI/MCP-focused guide for retrieving one Project Note.

---

## Related Documentation

| Guide | Link | Why It Matters |
|---|---|---|
| Project Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewProject.md` | Explains Projects as pseudo repositories / durable AI context containers. |
| GetProjectNotes | `https://revcent.com/documentation/markdown/mcp/operation/GetProjectNotes.md` | Retrieve a list of note titles and metadata before deciding which note content to fetch. |
| SearchProjectNotes | `https://revcent.com/documentation/markdown/mcp/operation/SearchProjectNotes.md` | Search Project Notes by keyword or phrase, optionally within a specific Project, when note content or history needs to be found quickly. |
| CreateProjectNote | `https://revcent.com/documentation/markdown/mcp/operation/CreateProjectNote.md` | Create Project Notes with both `title` and `content`. |
| EditProjectNote | `https://revcent.com/documentation/markdown/mcp/operation/EditProjectNote.md` | Correct or clarify an existing Project Note. |

---

## Operation Summary

Operation:

```text
GetProjectNote
```

Purpose:

```text
Retrieve one Project Note by Project Note ID, including the full note content.
```

Projects act as pseudo repositories for RevCent work, objectives, reporting efforts, external-agent context, and business operations. Project Notes are the durable history inside a Project. They allow AI/MCP to retrieve important context when needed instead of keeping all historical information in the active conversation.

Use `GetProjectNote` after `GetProjectNotes` identifies a relevant note by title and metadata, or after `SearchProjectNotes` finds a relevant note by keyword or phrase.

---


## Project Note Search Note

Use `SearchProjectNotes` when AI/MCP needs to find Project Note history by keyword, phrase, decision, warning, entity ID, or other text that may appear in note titles or content.

`SearchProjectNotes` requires `search_term` and can optionally include `project_id` to limit the search to one Project. Use it when keyword search is more efficient than paging through `GetProjectNotes` by date. If the workflow needs a canonical single-note retrieval afterward, use `GetProjectNote` with the returned Project Note ID.

---

## Title / Content / Metadata Caveat

Project Notes have a `title`, `content`, and optional `metadata`.

| Field | How AI/MCP Should Treat It |
|---|---|
| `title` | Short summary shown in note lists. Use it to decide whether the full note should be fetched. Max 100 characters. |
| `content` | Full note body. Use it for actual context, decisions, warnings, entity IDs, and follow-up details. Max 5000 characters. |
| `metadata` | Optional array of structured name/value pairs. Use it as filterable context such as entity type, entity ID, workflow, status, report period, decision category, risk level, or follow-up state. |

Important:

```text
GetProjectNote returns title, content, and metadata for one Project Note.
GetProjectNotes returns title/list metadata and supports metadata filtering, but does not return full content.
```

---

## Input Schema

| Field | Type | Required | Description |
|---|---:|---:|---|
| `project_note_id` | string | Yes | 20-character Project Note ID. |

---

## Metadata Property

Project Notes can include optional structured metadata as an array of name/value pairs.

Metadata item shape:

```json
{
  "name": "entity_type",
  "value": "payment_profile"
}
```

Metadata constraints:

| Field | Type | Required | Description |
|---|---:|---:|---|
| `name` | string | Yes | Metadata name. Minimum 1 character, maximum 100 characters. |
| `value` | string | Yes | Metadata value. Minimum 1 character, maximum 255 characters. |

Use metadata for compact, filterable context such as entity type, entity ID, workflow name, decision category, report period, agent purpose, risk level, or follow-up status. Metadata should not replace the `title` or `content`; it should add structured labels that make Project Notes easier to filter and retrieve later.

---

## Output Summary

`GetProjectNote` can return:

| Field | Meaning |
|---|---|
| `id` | 20-character Project Note ID. |
| `project` | Project object with Project ID and name. |
| `title` | Project Note title. |
| `content` | Full Project Note content. |
| `metadata` | Array of metadata name/value pairs associated with the Project Note. |
| `created_date_unix` | Note creation timestamp. |
| `updated_date_unix` | Note update timestamp. |

---

## When to Use

Use `GetProjectNote` when:

- the full content and metadata of a specific note is needed,
- a note title from `GetProjectNotes` appears relevant,
- AI/MCP needs to review context before acting,
- a note may be edited or deleted,
- the Project association of a note must be confirmed.

---

## Recommended Workflow

```text
GetProjectNotes or SearchProjectNotes
    ↓
Review note titles, metadata cues, and search highlights
    ↓
GetProjectNote for relevant note IDs
    ↓
Use the full content and metadata to understand context before acting
```

---

## Common Mistakes to Avoid

Do not:

- assume `GetProjectNotes` returned the full note content,
- edit or delete a note without first retrieving it with `GetProjectNote`,
- edit metadata without first reviewing the current metadata array,
- rely on title alone when the full note content may contain important warnings or decisions,
- ignore the Project association returned with the note.

---

## Final AI/MCP Instruction

Use `GetProjectNote` to retrieve the full content and metadata of one Project Note after identifying the note by ID. Treat the title as a short index label, the content as the actual durable context, and metadata as structured labels that help future retrieval and filtering.


---
Document Parent Directory
* [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.