Menu

Testing Capabilities

Test and preview API calls before connecting to Claude.

paso lets you test capabilities before connecting to an MCP client.

Preview capabilities

See what tools your declaration exposes:

usepaso inspect
Service:  github-api
Tools:    4
Protocol: MCP

  list_repos       List repositories for the authenticated user
  create_issue     Create an issue in a repository
  create_repo      Create a new repository
  delete_repo      Delete a repository

Dry run

Preview the exact request without sending it:

usepaso test list_repos -p per_page=5 --dry-run
--- DRY RUN (no request will be made) ---

GET /user/repos?per_page=5
Authorization: Bearer [REDACTED]

Use dry run to verify request structure, URL construction, and auth headers before hitting a real API.

Test with a real request

usepaso test list_repos -p per_page=5

Pass multiple parameters with repeated -p flags:

usepaso test create_issue -p owner=octocat -p repo=Hello-World -p title="Found a bug"

Authentication

Set the environment variable your declaration expects:

export GITHUB_TOKEN=ghp_xxxxx
usepaso test list_repos -p per_page=5

Or inline:

GITHUB_TOKEN=ghp_xxxxx usepaso test list_repos

Verbose output

See full request and response details:

usepaso test list_repos --verbose

Testing patterns

Read operations — safe to test freely. They don’t modify data.

usepaso test list_repos -p per_page=10

Write operations — preview first with --dry-run, then test against a staging environment or test account.

usepaso test create_issue \
  -p owner=test-org \
  -p repo=test-repo \
  -p title="Test issue" \
  --dry-run

Admin operations — dry run only against production. Test against disposable resources.

Your capabilities work.

You’ve verified that requests are correct before connecting to an MCP client.

Next, you might want to: