Skip to main content
Glama
nickknissen

Monta MCP Server

by nickknissen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MONTA_CLIENT_IDYesYour Monta API client ID
MONTA_CLIENT_SECRETYesYour Monta API client secret

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_charge_pointsA

Get a list of available EV charging points/stations.

Args:
    page: Page number for pagination (1-indexed, default: 1)
    per_page: Number of items per page (default: 10, min: 1, max: 100)

Returns:
    List of charge point dictionaries
get_charge_pointA

Get detailed information about a specific charging point.

Args:
    charge_point_id: The ID of the charge point to retrieve

Returns:
    Charge point details dictionary
get_chargesA

Get charging history/sessions for a charge point.

Args:
    charge_point_id: The ID of the charge point
    from_date: Filter charges from this date (ISO format, optional)
    to_date: Filter charges to this date (ISO format, optional)
    state: Filter by charge state (e.g., 'completed', 'active', optional)
    page: Page number for pagination (1-indexed, default: 1)
    per_page: Number of items per page (default: 10, min: 1, max: 100)

Returns:
    List of charge session dictionaries
start_chargeC

Start a charging session at a specific charge point.

Args:
    charge_point_id: The ID of the charge point to start charging

Returns:
    Charge session details dictionary or error response
stop_chargeA

Stop an active charging session.

Args:
    charge_id: The ID of the charge session to stop

Returns:
    Charge session details dictionary or error response
get_personal_walletA

Get personal wallet information including balance and payment details.

Returns:
    Wallet details dictionary
get_wallet_transactionsA

Get wallet transaction history with optional filtering.

Args:
    from_date: Filter transactions from this date (ISO format, optional)
    to_date: Filter transactions to this date (ISO format, optional)
    page: Page number for pagination (1-indexed, default: 1)
    per_page: Number of items per page (default: 10, min: 1, max: 100)

Returns:
    List of transaction dictionaries

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 7 tools

Disambiguation5/5

Every tool has a clearly distinct purpose: charge point listing vs detail, charging actions vs history, and wallet operations. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case (e.g., get_charge_points, start_charge). No mixed conventions.

Tool Count5/5

7 tools is well-scoped for an EV charging server, covering station info, session management, and financials without excess.

Completeness4/5

Core workflows are covered: listing/detailing stations, starting/stopping charges, viewing history, and wallet. Minor gap: no tool to get current charging status directly, but filterable in history.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources