MCP Resources

Resources are read-only contextual data that MCP clients can access to better understand the Monta Partner API. Unlike tools (which perform actions), resources provide reference information that helps AI assistants make more informed decisions.

Available Resources

`monta://terminology`

Type: JSON Purpose: API terminology and synonym mappings

This resource helps AI assistants understand common user terminology and map it to the correct Monta API concepts. For example, when a user says "chargers," the assistant knows to use the charge-points API endpoints.

Contents:

Canonical API term names
Common synonyms and alternative terms
Brief descriptions of each concept

Example mapping:

{
  "canonical": "charge-points",
  "synonyms": [
    "chargers",
    "charging stations",
    "EV chargers",
    "charging points",
    "stations",
    "EVSE"
  ],
  "description": "Electrical outlets that supply power for charging plug-in electric vehicles"
}

Use cases:

Understanding user intent when they use informal terminology
Mapping colloquial terms to API endpoint names
Learning domain-specific EV charging vocabulary

`monta://openapi`

Type: YAML Purpose: Complete OpenAPI specification for the Monta Partner API

This resource provides the full API specification, including:

All available endpoints and operations
Request/response schemas
Parameter definitions
Authentication requirements
Data models and types

Use cases:

Understanding API structure and capabilities
Validating request parameters
Exploring available operations
Reference for data types and schemas

How to Access Resources

Resources are accessed through the MCP protocol's resource endpoints. The exact method depends on your MCP client:

In Claude Desktop (SSE)

Resources are automatically available when you connect to the MCP server. Claude can read resources to understand the API context.

In n8n

Use the MCP Client tool with the "List Resources" or "Read Resource" operation:

List all resources:
- Tool: MCP Client
- Operation: resources/list
Read a specific resource:
- Tool: MCP Client
- Operation: resources/read
- URI: monta://terminology or monta://openapi

In Custom Integrations

Use the MCP protocol's resource handlers:

// List available resources
const resources = await client.listResources();

// Read a specific resource
const terminology = await client.readResource({
  uri: "monta://terminology"
});

const openapi = await client.readResource({
  uri: "monta://openapi"
});

Resource vs Tool vs Prompt

Feature	Resources	Tools	Prompts
Purpose	Provide context	Perform actions	Guide workflows
Type	Read-only data	API operations	Templates
When to use	Understanding concepts	Making API calls	Following best practices

Example scenario:

Resource: Read monta://terminology to understand that "chargers" = "charge-points"
Tool: Call get-charge-points to fetch the actual list of charge points
Prompt: Use restart-charge-points prompt for bulk restart workflow

Implementation Details

Resources are defined in the MCP server codebase:

Terminology: src/resources/terminology.ts
OpenAPI spec: Generated dynamically from the live API specification

Both resources are registered in src/utils/openapi/resource-generator.ts and automatically loaded when the MCP server starts.