Skip to main content
Glama
clicon

Clixon MCP Server

by clicon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
fetch_configB
Fetch network device configuration via RESTCONF.

Args:
    url: RESTCONF URL, e.g. https://device:8443/restconf/data
    username: HTTP basic auth username (optional).
    password: HTTP basic auth password (optional).
    verify_ssl: Whether to verify SSL certificates (default: False).
get_configA
Return the currently cached RESTCONF configuration.

Call fetch_config first to load configuration from a device.
get_config_pathA
Extract a specific section from the cached configuration by dot-separated path.

Args:
    path: Dot-separated path into the config, e.g.
          "ietf-interfaces:interfaces" or
          "ietf-interfaces:interfaces.interface"

Prompts

Interactive templates invoked by user choice

NameDescription
analyze_config Create a prompt to fetch and analyze device configuration.

Resources

Contextual data attached and managed by the client

NameDescription
server_info Return server metadata as JSON.
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 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: fetch_config retrieves configuration from a device, get_config accesses the cached configuration, and get_config_path extracts specific sections from the cache. There is no overlap or ambiguity in their functions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (fetch_config, get_config, get_config_path). The verbs 'fetch' and 'get' are semantically related but used distinctly to differentiate between external retrieval and internal access.

Tool Count3/5

With only 3 tools, the set feels thin for a network device configuration server, potentially lacking operations like update, delete, or validation. However, it covers basic fetch and query workflows, making it borderline but functional for limited use cases.

Completeness2/5

The toolset is severely incomplete for network device configuration management. It only supports fetching and reading configuration, with no tools for creating, updating, deleting, or validating configurations, leaving significant gaps that will hinder agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources