Semantic Pen MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Server capabilities have not been inspected yet.
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
Most tools have distinct purposes, but 'get_projects' and 'search_projects' could cause some confusion as both retrieve project information, though 'search_projects' adds filtering by name. The article-related tools (create_article, get_article, get_project_articles) are clearly differentiated by their specific actions and scopes.
All tools follow a consistent verb_noun naming pattern (e.g., create_article, get_article, get_project_articles, get_projects, search_projects). The structure is uniform throughout, using snake_case and clear action-object pairs, making the tool set predictable and easy to understand.
With 5 tools, the server is well-scoped for managing articles and projects, covering core operations without bloat. Each tool serves a clear purpose, such as creation, retrieval, and listing, which aligns with typical CRUD needs for this domain.
The tool set covers basic retrieval and creation for articles and projects, but there are notable gaps in update and delete operations. For example, there is no tool to update or delete articles or projects, which could limit agent workflows that require full lifecycle management.