Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRODUCTIVE_API_KEY | Yes | Your Productive API token | |
| PRODUCTIVE_TIMEOUT | No | Request timeout in seconds | 30 |
| PRODUCTIVE_BASE_URL | No | Base URL for Productive API | https://api.productive.io/api/v2 |
| PRODUCTIVE_ORGANIZATION | Yes | Your Productive organization ID |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quick_search | Quick search across projects, tasks, pages, and actions. This tool provides fast, comprehensive search across all Productive content types including projects, tasks, pages, and actions. It's optimized for quick lookups and general search queries. Returns: Search results from Productive API including: - Matching projects, tasks, pages, and actions - Relevance scores and metadata - Full entity details for each match Examples: quick_search("red") # Search for "red" across all content types quick_search("project", search_types=["project"]) # Search only in projects quick_search("meeting", deep_search=False) # Quick search without deep scan |
| get_recent_activity | Get a summarized feed of recent activities and updates. Returns recent changes, task updates, comments, new documents and activities in chronological order. Examples: get_recent_activity() # Last 24 hours, all activity get_recent_activity(hours=168) # Last week get_recent_activity(hours=48, project_id=343136) # Last 2 days on specific project get_recent_activity(hours=24, user_id=12345) # What a specific user did today get_recent_activity(hours=24, activity_type=1) # Only comments from last day get_recent_activity(hours=168, item_type='Task') # Task activities from last week get_recent_activity(hours=168, event_type='edit') # Task edits from last week get_tasks(extra_filters={'filter[status][eq]': 2}, sort='-updated_at', page_size=10) # Recently closed tasks |
| get_projects | Get all projects with basic information. Returns project data including:
|
| get_tasks | Get tasks with optional filtering and pagination. Supports filtering by project, assignee, status, and other criteria. All parameters are optional - omit to fetch all tasks. Example of extra_filters:
Returns: Dictionary of tasks matching the provided filters |
| get_task | Get detailed task information by its internal ID. Use this when you have the internal task ID (e.g., 14677418). For looking up tasks by their project-specific number (e.g., #960), use get_project_task instead. Returns task details including:
|
| get_task_history | Get comprehensive history for a specific task. Returns aggregated task history including:
Examples: get_task_history(14677921) # Default 30-day history get_task_history(14677921, hours=168) # Last week only get_task_history(14677921,1 hours=24) # Last 24 hours |
| get_comments | Get all comments across projects and tasks with full context. Returns comprehensive comment data including:
|
| get_todos | Get all todo checklist items across all tasks and projects. Returns comprehensive todo data including:
|
| get_todo | Get specific todo checklist item details with full task context. Returns detailed todo information including:
|
| get_pages | Get all pages/documents with optional filtering. Pages in Productive are documents that can contain rich text content, attachments, and are organized within projects. Returns: Dictionary containing pages with content, metadata, and relationships Example: get_pages(project_id=1234) # Get all pages for a specific project |
| get_page | Get specific page/document details with full content. Returns: Dictionary with complete page details including JSON-formatted content |
| get_people | Get all team members/people with optional pagination. Returns team member data including:
|
| get_person | Get detailed information about a specific team member/person. Returns comprehensive person details including:
|
| get_attachments | Get all attachments/files with optional filtering. Attachments are files (PDFs, images, documents) that can be associated with various Productive entities like tasks, comments, expenses, etc. Returns: Dictionary containing attachment metadata (name, type, size, relationships) Note: This provides metadata only, not actual file 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 | |