semantic-pen-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEMANTIC_PEN_API_KEY | Yes | Your Semantic Pen API key |
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 |
|---|---|
| get_projectsA | Get all projects from your article queue |
| get_project_articlesA | Get all articles from a specific project by project ID |
| search_projectsB | Search projects by name |
| create_articleB | Create a new article |
| get_articleA | Get a specific article by ID with full content |
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 5 tools
Each tool targets a distinct resource and action: list projects, list articles per project, search projects, create article, get article. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (get_projects, get_project_articles, search_projects, create_article, get_article), making the API predictable.
The server is scoped to a focused domain (projects and articles) and 5 tools is a reasonable, manageable number for this purpose.
The tool surface is read-heavy with only article creation. Missing operations include updating or deleting articles, creating/updating/deleting projects, and searching articles, which are significant gaps for full lifecycle management.