Skip to main content
Glama
smcdonnell7

Content Plan Builder

by smcdonnell7
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Content Plan Builder

An MCP (Model Context Protocol) server that generates comprehensive Asana project plans from arbitrary content — text, PDFs, DOCX files, meeting transcripts, or any combination.

Features

  • Multi-format Input: Accepts text, PDF, DOCX, TXT, MD, HTML, CSV, and JSON files

  • AI-Powered Generation: Uses Claude to create detailed project plans with:

    • 5 top-level tasks with 5-10 subtasks each

    • Realistic time estimates

    • Role-based assignments

    • Task dependencies

    • SMART goals

    • Key data points and metrics

  • Asana Integration: Optionally create projects directly in Asana

  • Flexible Output: Detailed structured format or compact array format

Related MCP server: task-manager-mcp

Installation

# Clone the repository
git clone https://github.com/yourusername/content-plan-builder.git
cd content-plan-builder

# Install dependencies
npm install

# Build
npm run build

Configuration

Environment Variables

Variable

Required

Description

ANTHROPIC_API_KEY

Yes

Anthropic API key for Claude

MCP Registration

Add to your ~/.mcp.json:

{
  "mcpServers": {
    "content-plan-builder": {
      "command": "node",
      "args": ["/path/to/content-plan-builder/dist/index.js"],
      "env": {
        "ANTHROPIC_API_KEY": "your-api-key"
      }
    }
  }
}

For Claude Desktop, add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "content-plan-builder": {
      "command": "node",
      "args": ["/path/to/content-plan-builder/dist/index.js"],
      "env": {
        "ANTHROPIC_API_KEY": "your-api-key"
      }
    }
  }
}

Usage

Tool: plan_from_content

Operations

Operation

Description

generate

Create a project plan from inputs

preview

Preview plan without saving

create

Generate plan and create in Asana

Parameters

Parameter

Type

Description

operation

string

generate, preview, or create

inputs

array

Array of input objects

knowledgeBaseContext

string

Additional context to include

projectName

string

Name for the generated project

creativity

string

conservative, balanced, or expansive

outputFormat

string

detailed, compact, or both

asanaAccessToken

string

Asana PAT (for create operation)

asanaTeamGid

string

Team GID for new project

targetProjectGid

string

Add to existing project

Input Types

Type

Description

text

Raw text content

file

File path to PDF, DOCX, TXT, MD, HTML, CSV, or JSON

transcript

Meeting transcript text

meeting_notes

Meeting notes text

Examples

Generate plan from text

{
  "operation": "generate",
  "inputs": [
    {
      "type": "text",
      "content": "We need to build a new customer portal with user authentication, a dashboard showing order history, and the ability to track shipments..."
    }
  ],
  "projectName": "Customer Portal Development"
}

Generate from file

{
  "operation": "generate",
  "inputs": [
    {
      "type": "file",
      "content": "/path/to/requirements.pdf"
    }
  ],
  "creativity": "expansive"
}

Combine multiple inputs

{
  "operation": "generate",
  "inputs": [
    {
      "type": "transcript",
      "content": "Meeting transcript from kickoff call..."
    },
    {
      "type": "file",
      "content": "/path/to/scope-document.docx"
    }
  ],
  "knowledgeBaseContext": "This project is part of the Q2 digital transformation initiative...",
  "projectName": "Digital Transformation - Phase 1"
}

Create in Asana

{
  "operation": "create",
  "inputs": [
    {
      "type": "transcript",
      "content": "Sprint planning meeting transcript..."
    }
  ],
  "projectName": "Sprint 14 Tasks",
  "asanaAccessToken": "your-asana-pat",
  "asanaTeamGid": "1234567890"
}

Output Formats

Detailed Format

Full structured plan with all metadata:

{
  "projectGoal": "Build a customer-facing portal that enables...",
  "topLevelTasks": [
    {
      "name": "User Authentication System",
      "description": "Implement secure authentication...",
      "assignedTo": "Senior Developer",
      "estimate": "2 weeks",
      "blockedBy": "N/A",
      "subtasks": [...]
    }
  ],
  "keyDataPoints": ["500 concurrent users expected", ...],
  "keywordsAndPhrases": ["customer portal", "authentication", ...],
  "questionsAndExercises": ["What is the expected user growth rate?", ...],
  "smartGoals": ["Reduce customer support tickets by 30% within 3 months", ...],
  "additionalMaterials": ["UX design guidelines", ...]
}

Compact Format

Array of all subtasks for easy import:

[
  {
    "index": 1,
    "Parent-task": "User Authentication System",
    "Sub-Task": "Design authentication flow",
    "Task Description": "Create detailed flow diagrams...",
    "Assignee": "UX Designer",
    "Estimated Time": "3 days",
    "Dependencies": "N/A"
  }
]

Creativity Levels

Level

Description

conservative

Stick closely to what is explicitly mentioned in the content

balanced

Include tasks that are mentioned or strongly implied (default)

expansive

Infer additional tasks for testing, documentation, deployment, etc.

Development

# Run in development mode
npm run dev

# Build
npm run build

# Start production server
npm start

License

MIT

Available Tools

1 tool
plan_from_contentA

Generate Asana project plans from arbitrary content (text, PDF, DOCX, transcripts).

This tool accepts various input types and uses AI to create comprehensive project plans with:

  • 5 top-level tasks with 5-10 subtasks each

  • Time estimates and role assignments

  • Task dependencies

  • SMART goals and key data points

Operations:

  • generate: Create a plan from inputs

  • preview: Preview plan without creating in Asana

  • create: Generate plan and create project in Asana

Call without parameters for interactive discovery.

ParametersJSON Schema
NameRequiredDescriptionDefault
operationNoOperation to perform
inputsNoArray of content inputs
knowledgeBaseContextNoAdditional context to include in generation
projectNameNoName for the generated project
creativityNoCreativity level for AI generation
outputFormatNoOutput format preference
asanaAccessTokenNoAsana personal access token (for create operation)
asanaTeamGidNoAsana team GID for new project
targetProjectGidNoAdd to existing Asana project instead of creating new

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the tool's operations and output structure but lacks details on permissions, rate limits, error handling, or whether 'create' requires authentication (though asanaAccessToken parameter hints at this). It adds some context but doesn't fully cover behavioral traits for a complex tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and appropriately sized, with clear sections for purpose, plan details, operations, and a call-to-action. Every sentence adds value, though it could be slightly more concise by integrating some details more tightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (9 parameters, no annotations, no output schema), the description is moderately complete. It covers purpose and operations but lacks details on authentication requirements, error conditions, output format specifics, or how the AI generation works. Without annotations or output schema, more behavioral context would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 9 parameters. The description adds minimal parameter semantics by mentioning 'arbitrary content' and listing content types, but doesn't provide additional meaning beyond what the schema provides. The baseline of 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Generate Asana project plans from arbitrary content (text, PDF, DOCX, transcripts)' with specific details about what the plans include (5 top-level tasks with subtasks, time estimates, role assignments, dependencies, SMART goals). It distinguishes itself by specifying content types and plan structure, though no siblings exist for comparison.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage guidance by listing three operations (generate, preview, create) with brief explanations, and mentions 'Call without parameters for interactive discovery.' However, it doesn't explicitly state when to use each operation versus alternatives or provide exclusions, which prevents a perfect score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedplan_from_content
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.8/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'plan_from_content' has a single, clearly defined purpose of generating Asana project plans from content, making disambiguation perfect.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'plan_from_content' follows a clear verb_noun pattern (plan from content), and there are no other tools to cause inconsistency.

Tool Count2/5

A single tool for a server named 'Content Plan Builder' feels too thin for the apparent scope. The tool handles multiple operations (generate, preview, create), but these are bundled into one tool, suggesting the server might be under-scoped. Typically, such operations could be separate tools for better modularity and clarity.

Completeness3/5

The tool covers core generation and creation operations for Asana project plans, but there are notable gaps. For example, there are no tools for updating, deleting, or managing existing plans, which are common in project management domains. This could lead to dead ends for agents trying to modify or remove plans.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smcdonnell7/content-plan-builder'

If you have feedback or need assistance with the MCP directory API, please join our Discord server