getcited
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEO_API_KEY | Yes | The key from Settings → API keys. | |
| SEO_API_URL | No | Endpoint override. Defaults to https://app.getcited.dev/api/mcp. | https://app.getcited.dev/api/mcp |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| how_to_authenticateA | This server is not authenticated, so none of its SEO tools are loaded. Call this for the exact steps to fix it. Retrying other tools will not help. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool is exposed, so there is no possibility of confusing it with another operation. Its purpose as an authentication helper is clearly stated.
The single tool name how_to_authenticate is descriptive and readable, but there is no established pattern to evaluate since it is the only tool. It does not follow a typical verb_noun naming convention.
A single authentication helper is far too few for a server meant to provide SEO tools. The current toolset is essentially a placeholder rather than a functional suite.
The intended SEO tools are entirely absent; the only available tool tells agents how to authenticate. This leaves the server's core domain completely uncovered and any real task impossible to complete.