Schema | mcp-plots

mcp-plots

Overview Schema Source Related Servers Discussions Admin

Server Configuration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`MCP_HOST`	No	Host address	0.0.0.0
`MCP_PORT`	No	Port number	8000
`LOG_LEVEL`	No	Logging level: DEBUG, INFO, WARNING, ERROR, CRITICAL	INFO
`MCP_DEBUG`	No	Enable debug mode: true or false	false
`MCP_TRANSPORT`	No	Transport type: streamable-http or stdio	streamable-http
`CHART_DEFAULT_DPI`	No	Default chart DPI	100
`CHART_DEFAULT_WIDTH`	No	Default chart width in pixels	800
`CHART_DEFAULT_HEIGHT`	No	Default chart height in pixels	600
`CHART_MAX_DATA_POINTS`	No	Maximum data points per chart	10000

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

Name Description

Name	Description
configure_preferencesA	`Interactive configuration tool for setting user preferences. Parameters: - output_format: "mermaid", "mcp_image", or "mcp_text" - theme: "default", "dark", "seaborn", "minimal", etc. - chart_width: Chart width in pixels - chart_height: Chart height in pixels - reset_to_defaults: Reset all preferences to system defaults If no parameters provided, shows current configuration with sample.`
render_chartA	Render a chart from tabular data and return MCP-compatible content. Special modes: - chart_type="help": Returns available chart types, themes, and field suggestions - chart_type="suggest": Analyzes your data and suggests field mappings (requires data) Parameters: - chart_type: chart type ("line", "bar", "pie", etc.) or "help"/"suggest" - data: list of objects (rows) - optional for help mode - field_map: keys like x_field, y_field, category_field, value_field, group_field, size_field - config_overrides: subset of ChartConfig as dict (width, height, title, theme, dpi, etc.) - options: generator-specific options (e.g., smooth, stack) - output_format: MCP_IMAGE (PNG), MCP_TEXT (SVG), or MERMAID

configure_preferencesA

    Interactive configuration tool for setting user preferences.
    
    Parameters:
    - output_format: "mermaid", "mcp_image", or "mcp_text"
    - theme: "default", "dark", "seaborn", "minimal", etc.
    - chart_width: Chart width in pixels
    - chart_height: Chart height in pixels  
    - reset_to_defaults: Reset all preferences to system defaults
    
    If no parameters provided, shows current configuration with sample.

render_chartA

    Render a chart from tabular data and return MCP-compatible content.
    
    Special modes:
    - chart_type="help": Returns available chart types, themes, and field suggestions
    - chart_type="suggest": Analyzes your data and suggests field mappings (requires data)

    Parameters:
    - chart_type: chart type ("line", "bar", "pie", etc.) or "help"/"suggest"
    - data: list of objects (rows) - optional for help mode
    - field_map: keys like x_field, y_field, category_field, value_field, group_field, size_field
    - config_overrides: subset of ChartConfig as dict (width, height, title, theme, dpi, etc.)
    - options: generator-specific options (e.g., smooth, stack)
    - output_format: MCP_IMAGE (PNG), MCP_TEXT (SVG), or MERMAID

Prompts

Interactive templates invoked by user choice

Name	Description
`visualization_guide`	Comprehensive instructions for using visualization tools in this MCP server. Provides step-by-step workflow guidance for generating charts from data, including tool usage patterns, field mapping strategies, and optimization tips for the best user experience. Returns: str: Detailed workflow instructions and best practices

Resources

Contextual data attached and managed by the client

Name	Description
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.7/5.0

Scored 2026-04-18 08:25 across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes with no overlap: configure_preferences handles user settings and defaults, while render_chart focuses on data visualization and chart generation. An agent would never confuse these tools as they address separate concerns in the plotting workflow.

Naming Consistency4/5

Both tools follow a consistent verb_noun pattern (configure_preferences, render_chart) with clear action-object naming. The minor deviation is that 'configure' and 'render' are different verb types, but the pattern remains readable and predictable throughout the set.

Tool Count2/5

With only 2 tools for a plotting server, the surface feels severely under-scoped. While the tools cover configuration and rendering, there are obvious gaps in data manipulation, chart editing, export options, and batch operations that would be expected in a complete plotting toolkit.

Completeness2/5

The toolset is significantly incomplete for a plotting domain. Missing are essential operations like data transformation/cleaning, chart modification/updating, saving/exporting beyond immediate rendering, template management, and batch processing. Agents will hit dead ends when trying to perform common plotting workflows beyond basic render-and-configure.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

GitHub Repository

Need Help?

Related Servers