What are MCP Resources?
MCP Resources provide AI agents with structured, domain-specific knowledge about Ekso. Unlike tools (which perform actions), resources serve read-only reference content that helps AI agents understand Ekso’s data model, terminology, and workflows. Resources are accessed via the standard MCPresources/list and resources/read methods. Each resource returns Markdown content optimized for AI consumption — concise, structured, and focused on the information an agent needs to use Ekso effectively.
Available resources
| URI | Name | Description |
|---|---|---|
ekso://guide/overview | Ekso Overview | Core concepts, entity relationships, and terminology |
ekso://guide/item | Item & Work | Work items: keys, lifecycle, fields, dependencies |
ekso://guide/container | Container & Area | Containers, areas, labels, organizational hierarchy |
ekso://guide/field | Field & Data Type | Custom/system fields, data types, list values |
ekso://guide/process | Process & Workflow | Process definitions, status workflows, transitions |
ekso://guide/planning | Planning & Delivery | Boards, cycles, budget tracking, resource assignment |
ekso://guide/time-and-finance | Time & Finance | Time tracking, billable codes, cost centers, profitability |
ekso://guide/collaboration | Collaboration | Annotations, links, watches, documents, folders |
ekso://guide/administration | Administration | Users, groups, access control, constraints, rules |
ekso://guide/filter-syntax | Filter Syntax | Item filter conditions, operators, grouping logic |
Characteristics
- Read-only — Resources are purely informational. They do not create, update, or delete any data.
- Stateless — Each
resources/readcall returns the full content for that resource. There is no pagination or session state. - Markdown content — All resources return Markdown-formatted text designed for AI agent consumption.
Usage
AI agents typically read one or more resources at the start of a session to build context about the Ekso domain before invoking tools. For example, an agent might readekso://guide/item to understand item fields and lifecycle before calling create_item or search_items.