Skip to main content
Glama
linkcd

Tibber MCP

by linkcd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Tibber MCP

No user-submitted related servers found.

    Related Servers

    • euenergy-mcp

      adambenhassen
      F
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server that exposes European day-ahead electricity prices for ~41 bidding zones via tools like hourly prices, cheapest hours, current price, and cross-zone summary, enabling AI agents to query energy market data.
      1
      -

    • Monta MCP Server

      nickknissen
      F
      license
      A
      quality
      D
      maintenance
      MCP server that enables LLMs to interact with Monta's EV charging platform for managing charge points, charging sessions, and wallet operations.
      7
      -

    • emoncms-mcp-server

      guibrazlima
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for EmonCMS energy monitoring API, enabling AI assistants to query energy feeds, inputs, and historical data.
      1
      -

    • Tigo Energy MCP Server

      matt-dreyer
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that provides comprehensive access to Tigo Energy solar system data and analytics. It enables AI assistants to interact with your Tigo solar monitoring system to retrieve production data, performance metrics, system health information, and maintenance insights.
      MIT
    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

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one focuses on consumption data (historical usage and costs), while the other focuses on price information and home details (current, forecasted pricing and location/timezone). There is no overlap in functionality, making it easy for an agent to select the correct tool based on the query.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive names (get_consumption_data and get_price_and_home_info). The naming is predictable and readable, adhering to a clear convention throughout the set.

    Tool Count3/5

    With only 2 tools, the server feels thin for a domain like energy/utility management, which typically involves more operations such as setting preferences, controlling devices, or accessing billing history. While the tools cover key data retrieval aspects, the count is borderline low for comprehensive agent interaction.

    Completeness3/5

    The tools provide good read-only coverage for consumption and pricing data, but there are notable gaps: no update/delete operations, no ability to manage home settings or devices, and no support for actions like adjusting energy usage or handling billing. This limits the server to data retrieval only, which may cause agent failures in broader utility management tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources