Paydirt MCP server

Read from the package source without running it. The installed server may list more.

• paydirt_add_feedback_form

  Use this when the user asks for a named feedback form at a screen, button, lifecycle moment, or in-app action. Creates or reuses a normalized-title match, preserves the placement verbatim, optionally resolves Slack, and returns exact Swift plus mandatory edit/build/test actions. Remote form creation alone is not completion.

• paydirt_ask

  Use this when the user asks a natural-language analytical question about their Paydirt feedback, such as pricing themes or feature requests. Reads actual responses and returns analysis without taking action.

• paydirt_begin_setup

  Use this when installing Paydirt for a new user, machine, or iOS app. Inspect the host first. Without form_plan_confirmed, returns the concise cancellation/Suggest a Feature confirmation and does not start authorization. After confirmation, pass the selected use_cases and placement to receive authorization_url and finish_arguments immediately.

• paydirt_connect_slack

  Use this when the user asks to connect Slack or repair Slack delivery after onboarding. Returns the Slack OAuth URL. Authorization provisions #paydirt-suggest-a-feature for feature forms and #paydirt-cancellations for trial and subscription cancellation forms, then assigns each form automatically when workspace policy allows it.

• paydirt_create_appwrite action

  Use this when the user explicitly needs a separate Paydirt app and setup cannot reuse or create it. Creates a new app; list existing apps first when duplication is possible.

• paydirt_create_formwrite action

  Use this when creating a low-level remote form without a host-app placement request. First confirm a matching form does not exist. Map subscription cancellation to cancellation, trial cancellation to trial_expiration, and regular feedback to custom; then wire the returned ID into iOS and assign Slack. Prefer paydirt_add_feedback_form for named screen or action placement.

• paydirt_delete_formwrite action

  Use this when the user explicitly asks to permanently delete a specific Paydirt form. This is destructive and should only be called after inspecting the form when its identity is uncertain.

• paydirt_finish_setup

  Use this when the user has opened the authorization URL returned by paydirt_begin_setup. Checks one setup session and returns immediately. If pending, do not loop or sleep. When ready, securely saves credentials and returns the host-app build, visible verification, and post-verification delivery-choice contract.

• paydirt_get_app

  Use this when the agent needs the current identity, bundle ID, SDK key, or configuration for one known Paydirt app. Does not modify the app.

• paydirt_get_feedback_digest

  Use this when the user or a scheduled task needs a read-only daily or periodic Paydirt brief. Returns completed-response totals by feedback type, comparison with the previous equal period, and concise highlights. Never turn feedback into code changes or tasks automatically.

• paydirt_get_form

  Use this when the agent needs the current prompt, type, enabled state, or Slack assignment for one known form. Does not modify the form.

• paydirt_get_responses

  Use this when the user or coding agent needs raw feedback conversations, exact Q/A turns, input type, subscription metadata, or a read-only inbox cursor. Defaults to completed conversations. Use since plus the newest updated_at for incremental reads; never take action from responses automatically.

• paydirt_get_summary

  Use this when the user asks for an aggregate AI summary of recent Paydirt responses. Raw questions and answers remain the source of truth; this read-only summary is supplementary.

• paydirt_health_check

  Use this when diagnosing whether the Paydirt API is reachable and stored authentication is valid. Performs a read-only connectivity check.

• paydirt_list_apps

  Use this when the user asks which Paydirt apps exist or when an agent must resolve an app ID after setup. Lists all apps for the authenticated Paydirt account without changing them.

• paydirt_list_forms

  Use this when the user asks which forms exist or the agent needs to resolve or deduplicate forms for a Paydirt app. Does not modify forms.

• paydirt_list_slack_channels

  Use this when Slack is connected and the agent must resolve a requested channel name to its channel ID. Lists available channels without changing assignments.

• paydirt_set_form_channel

  Use this when a form must deliver completed conversations to a specific Slack channel ID. Replaces that form’s current channel assignment and should be verified afterward.

• paydirt_setup

  Use this when an older client expects the single setup tool. Without session_id it starts setup and immediately returns authorization_url plus finish arguments; with session_id it checks once and returns pending, expired, or the complete installation contract. It never opens a browser or blocks. New agents should prefer paydirt_begin_setup and paydirt_finish_setup.

• paydirt_slack_status

  Use this when the developer selected Slack or combined delivery and completed authorization. Reports the Paydirt feedback channel and whether every installed form is assigned. Do not call it for agent-only delivery.

• paydirt_toggle_form

  Use this when the user asks to enable or disable an existing form remotely. Disabled forms are not shown by the SDK; calling again with the opposite value reverses the change.

• paydirt_update_appwrite action

  Use this when the user asks to change an existing Paydirt app’s identity, bundle ID, description, or AI context. Only supplied fields are updated.

• paydirt_update_formwrite action

  Use this when the user asks to change an existing form’s name, initial question, or AI follow-up guidance. Only supplied fields are updated.

• Code scan10 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 18 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

91/100

higher than 88% of 4,460 AI and agents servers

Tools

23

the typical AI and agents server has 6

Tools that change things

22%

typical: 0%. Fewer write tools means less an agent can break

Downloads a week

59

more than 49% of 1,538 AI and agents servers with a package

Paydirt: common questions

Is Paydirt MCP server safe?

Yes, by our scan: it is graded A (91/100). Read the Paydirt safety report

How do I install Paydirt?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Paydirt need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Paydirt maintained?

The last commit was 19 days ago (2026-10-16). The latest release is v2.3.0.

What can I use instead of Paydirt?

Servers from other publishers that do the same job: agent-device MCP server, DCC-MCP Core MCP server and agent-device MCP server.

How does Paydirt compare with other AI and agents MCP servers?

safety score 91/100 (higher than 88% of 4,460 AI and agents servers); tools 23 (the typical AI and agents server has 6); tools that change things 22% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.