monta-api
Core knowledge for working with the Monta API through the Monta MCP tools. Use whenever the user asks about Monta, EV charge points, chargers, charging sessions, sites, teams, wallets, price groups, charge auth tokens, or webhooks, or when calling any get-*, post-*, patch-*, put-*, or delete-* Monta tool. Covers the domain model, auth and scopes, pagination, dates, rate limits, and which operations need confirmation.
Install
With your agent
Install OMGSkills skill "monta-app/claude-plugin-monta:skills/monta-api" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/monta-app/claude-plugin-monta /tmp/claude-plugin-monta && ln -s /tmp/claude-plugin-monta/skills/monta-api ~/.claude/skills/monta-apiFrom README
Monta API Monta is a platform for operating EV charging infrastructure. The MCP server exposes one tool per Monta API endpoint, named after the endpoint's operation ID (get-charge-points, get-charge, post-charge-point, delete-team, and so on). Full reference: developer.monta.com. Tools are often deferred because there are several hundred of them: when a tool such as get-sites is not in your visible list, search for it by operation ID and load it. Only conclude a tool is unavailable after searching, and then check the credential's scopes with get-current-consumer. Read references/endpoints.md for the task-to-endpoint map and the full safety classification. Read references/conventions.md for auth, pagination, dates, errors, and webhooks in detail. Domain model Operator: the CPO or business partner that owns the API credential. get-current-consumer returns operatorId and optional teamIds restrictions. Team: the account that owns charge points and pays or gets paid.