Your First MCP Session: A Repeatable Smoke Test Script
Verify your MCP setup works correctly with this step-by-step smoke test. This guide walks you through listing tasks, reading task details, adding comments, and optionally testing time tracking—all with expected outputs and troubleshooting steps if anything fails.
What This Guide Covers
This smoke test validates your MCP integration end-to-end:
Test Steps
- List tasks: Verify read access to your workspace
- Read a task: Test retrieving specific task details
- Add a comment: Verify write permissions work
- Time tracking (optional): Test timer start/stop functionality
Prerequisites
Before running the smoke test, ensure you have:
- MCP client configured (Claude Desktop, Cursor, Windsurf, or Continue)
- Corcava MCP server added to your client configuration
- API key with read and write permissions
- At least one task in your Corcava workspace
- Client restarted after configuration changes
Step-by-Step Smoke Test
Step 1: List Tasks
Start with a simple read operation to verify connection:
Test Prompt
Expected Output:
What the AI does:
- Calls
list_tasksMCP tool - Receives task list from Corcava
- Formats and displays results
⚠️ If This Fails:
- Check API key is correct and active
- Verify MCP server configuration
- Ensure client was restarted after config changes
- See Tools Not Listed
Step 2: Read One Task
Test retrieving specific task details:
Test Prompt
Expected Output:
What the AI does:
- Calls
get_taskwith task ID - Retrieves full task details
- Displays formatted information
⚠️ If This Fails:
- Verify task ID is correct (copy from step 1 output)
- Check API key has read permissions
- Ensure task exists in your workspace
Step 3: Add a Comment
Test write permissions by adding a comment:
Test Prompt
Expected Output:
What the AI does:
- Calls
add_task_commentwith task ID and comment text - Confirms comment was added
- Verifies write permissions work
⚠️ If This Fails:
- Check API key has write permissions
- Verify task ID is correct
- See 401 Unauthorized
- See 403 Forbidden
Step 4: Time Tracking (Optional)
Test time tracking functionality with confirmation:
Test Prompt
Expected Output:
Stop Timer Prompt:
What the AI does:
- Calls
get_taskto show task details - Calls
start_time_trackingto start timer - Later: calls
stop_time_trackingandadd_task_comment
⚠️ If This Fails:
- Check API key has time tracking permissions
- Verify no other timer is already running
- See Tool Call Failures
Complete Smoke Test Script
Here's the complete script you can copy and run:
Full Test Sequence
1. List Tasks
2. Read Task
3. Add Comment
4. Time Tracking (Optional)
Verification Checklist
Success Criteria
- ✅ Tasks list returns results without errors
- ✅ Task details retrieved successfully
- ✅ Comment added and visible in Corcava
- ✅ Timer starts and stops without errors (if tested)
- ✅ All operations complete in reasonable time (<5 seconds each)
Troubleshooting First-Run Issues
No Tools Available
Symptom: AI says no MCP tools are available
Fix:
- Verify MCP server is configured in client settings
- Check config file JSON is valid
- Restart client completely (not just reload)
- See Tools Not Listed
Authentication Errors
Symptom: 401 or 403 errors on tool calls
Fix:
- Verify API key is correct in config
- Check Authorization header format: "Bearer YOUR_KEY"
- Ensure API key is active in Corcava
- See 401 Troubleshooting
Related Resources
MCP Quickstart
5-minute setup guide
Troubleshooting Index
Complete troubleshooting guide
Weekly Planning
First workflow to try
Health Checks
Verify server status
Complete Your First MCP Session
Run the smoke test to verify your MCP setup works correctly