Claude Writer's Aid MCP
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 |
|---|---|
| search_contentC | Semantic search across all manuscript content |
| find_related_sectionsC | Find content semantically similar to given text |
| extract_themesC | Cluster content into main themes/topics |
| track_concept_evolutionC | Show how concept is discussed across documents |
| find_gapsC | Find terms mentioned but not explained |
| generate_outlineC | Create hierarchical outline from content |
| suggest_reorganizationC | Suggest better content organization |
| find_orphaned_sectionsC | Find sections with no incoming links |
| validate_structureC | Check heading hierarchy and section balance |
| analyze_link_graphC | Visualize connections between documents |
| find_broken_linksC | Detect broken internal and external links |
| suggest_cross_referencesC | Suggest where to add links between sections |
| trace_reference_chainC | Follow concept through linked documents |
| check_terminologyC | Find inconsistent term usage |
| find_todosC | Extract all TODO/FIXME/DRAFT markers |
| check_readabilityC | Analyze readability metrics |
| find_duplicatesC | Find near-duplicate content |
| get_writing_statsC | Overall project statistics |
| track_changesC | Show what changed since timestamp |
| generate_progress_reportC | Create progress dashboard |
| recall_writing_sessionC | Search writing session history by date range or query |
| get_session_contextC | Get detailed context for a specific file or concept from past sessions |
| list_writing_decisionsC | List writing decisions by file, type, or date range |
| mark_mistakeC | Record a writing mistake to avoid repeating it |
| search_similar_mistakesC | Search for similar mistakes to avoid repeating them |
| set_requirementC | Store a publisher or style requirement |
| get_requirementsC | Get all requirements or filter by type |
| add_style_decisionC | Record a style decision for consistency |
| track_file_evolutionC | Show how a file evolved through git commits with rationale |
| track_concept_evolutionC | Track how a concept's definition evolved over time |
| find_concept_contradictionsC | Detect contradictions in concept definitions across versions |
| link_commits_to_sessionsC | Link git commits to writing sessions for context |
| holistic_searchC | Unified search across all memory layers (content, decisions, mistakes, concepts, sessions, commits) |
| get_file_contextC | Get all context for a file (sessions, decisions, mistakes, commits) |
| check_before_editB | Check context before editing a file - get warnings about past mistakes, decisions, and requirements to maintain consistency |
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 34 tools
Most tools have distinct purposes focused on different aspects of writing analysis and project management, such as link analysis (analyze_link_graph), consistency checking (check_terminology), and evolution tracking (track_concept_evolution). However, some tools like 'search_content' and 'holistic_search' could potentially overlap in function, and 'get_file_context' and 'get_session_context' might be confused for similar context retrieval tasks, though their descriptions help differentiate them.
Tool names follow a highly consistent verb_noun pattern throughout, using snake_case uniformly. Examples include 'add_style_decision', 'check_readability', 'find_duplicates', 'generate_outline', and 'track_changes'. This predictability makes it easy for agents to understand and select tools based on their naming conventions.
With 34 tools, the count feels excessive for a writing aid server, leading to potential overwhelm and redundancy. While the domain is broad (covering analysis, tracking, and management), many tools could be consolidated (e.g., multiple search and tracking functions), making the set feel heavy and less scoped than ideal for efficient agent use.
The tool set provides comprehensive coverage for writing and project management, including CRUD-like operations (e.g., 'set_requirement', 'mark_mistake'), analysis (e.g., 'check_readability', 'extract_themes'), tracking (e.g., 'track_changes', 'track_concept_evolution'), and search functionalities. There are no obvious gaps; agents can perform end-to-end workflows from planning to validation without dead ends.