Skip to main content
Glama
SavageCore

dashy-mcp

by SavageCore
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DASHY_URLYesThe URL of your Dashy instance (required).
DASHY_TOKENNoOptional API token for Dashy. If not set, no auth header is sent.
DASHY_CONFIG_FILENoThe config file to use. Defaults to 'conf.yml'.conf.yml

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": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
dashy_configA

dashy config operations on Dashy. Pass operation and an arguments dict matching that operation's parameters.

  • dashy_get_config(filename='') — Get a full Dashy config file as JSON. Defaults to conf.yml.

  • dashy_list_config_files() — List the YAML config files available on the Dashy instance.

  • dashy_replace_config(config, filename='') — Replace an entire Dashy config file. config must be a full config object (pageInfo, appConfig, sections, pages) -- this is a complete overwrite, not a merge.

dashy_keyA

dashy key operations on Dashy. Pass operation and an arguments dict matching that operation's parameters.

  • dashy_get_key(key, filename='') — Get one top-level config key: pageInfo, appConfig, sections, or pages.

  • dashy_set_key(key, value, filename='') — Replace one top-level config key (pageInfo, appConfig, sections, or pages) with value. This is a complete replacement of that key, not a merge.

dashy_sectionA

dashy section operations on Dashy. Pass operation and an arguments dict matching that operation's parameters.

  • dashy_add_section(section, filename='') — Add a new section (a group of tiles) to the dashboard. section requires a name; common keys: name, icon, items, displayData.

  • dashy_delete_section(sid, filename='') — Delete a section (by index or exact name), including all its items.

  • dashy_get_section(sid, filename='') — Get one section by zero-based index or exact section name.

  • dashy_update_section(sid, patch, filename='') — Shallow-merge patch into a section (by index or exact name). Only the given fields change; a nested array in patch replaces the existing one wholesale.

dashy_itemA

dashy item operations on Dashy. Pass operation and an arguments dict matching that operation's parameters.

  • dashy_add_item(sid, item, filename='') — Add a new item (tile) to a section (by index or exact name). item requires a title; common keys: title, url, icon, description, target.

  • dashy_delete_item(sid, iid, filename='') — Delete an item (tile) by index or exact title, within a section by index or exact name.

  • dashy_get_item(sid, iid, filename='') — Get one item (tile) by index or exact title, within a section by index or exact name.

  • dashy_list_items(sid, filename='') — List the items (tiles) in a section, by section index or exact name.

  • dashy_update_item(sid, iid, patch, filename='') — Shallow-merge patch into an item (by index or exact title), within a section (by index or exact name). Only the given fields change.

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

A4/5.0

Scored across 4 tools

Disambiguation4/5

The four tools target distinct levels of the Dashy config hierarchy (config file, top-level keys, sections, items). While there is some overlap—e.g., dashy_key can get/set the 'sections' key—the intended granularity is clear. A minor ambiguity exists because key operations could be used to access sections/items, but the descriptions guide toward the resource-specific tools.

Naming Consistency4/5

All tool names follow a consistent dashy_<noun> pattern (config, key, section, item), which is predictable. The operation names embedded within each tool also use consistent verb_noun snake_case (e.g., get_config, add_section, delete_item). The only deviation is that the tool names are nouns rather than verbs, but this is uniform across the set.

Tool Count4/5

Four tools is slightly few for a config management server, but each tool is a dispatcher covering multiple related operations, so the effective scope is broader. This keeps the tool count within a reasonable range and avoids overwhelming the agent with 18 separate tools.

Completeness4/5

The server covers the primary lifecycle for config management: reading/replacing full configs, getting/setting top-level keys, and CRUD for sections and items. Notable missing operations include a list_sections function, but sections can be retrieved via get_config or get_key, and the rest of the surface is functional.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources