Promptless provides visibility into how AI agents interact with websites and APIs, capturing browser actions, network requests, tool calls, and execution traces. Inspect agent workflows, debug failed interactions, analyze behavior, and identify issues in autonomous web automation.
VS Code
Try asking
Encrypted at rest, isolated from the model
Resolved from an AES-256-GCM vault at the moment of the call and attached to the request — the model never sees the secrets.
Ask Promptless to update your documentation. Promptless researches the affected docs and proposes changes when needed. Returns a trigger_event_id right away, but the work itself takes several minutes. The response includes the next_call for following the submitted work with wait_for_task_update. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#submit_documentation_task
Ask Promptless to change a suggestion it already produced, the same as the Request Changes button in the Promptless dashboard. Any changes apply to that suggestion and its existing pull request if one is open. To make the edit yourself instead, edit that pull request directly — its URL is the suggestion's docs_pr_url. Takes a suggestion id from search_suggestions or get_task_status and returns a trigger_event_id for the new task. Use submit_documentation_task when no suggestion exists yet, and when the suggestion is closed or merged and can no longer be changed. The response includes next_call for following the submitted work with wait_for_task_update. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#request_changes
Change a suggestion's own fields and open its documentation pull request. Set the title, labels, or assignees, and pass open_pull_request to publish the branch as a pull request you can review and edit directly. Every argument is optional except suggestion_id; an omitted field is left alone. Supplying labels or assignees replaces the whole list, so read the current values from search_suggestions or get_task_status first. A new title is also pushed to the suggestion's pull request while that pull request is open, so the two never disagree; if the host rejects the push, the stored title is left unchanged. Opening is idempotent: a suggestion already carrying a pull request returns it rather than opening a second, and draft state follows the organization's source-pull-request policy. Use request_changes to ask Promptless to rewrite the documentation itself. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#update_suggestion
Close a suggestion and its documentation pull request, ending the review without shipping it. Use it to reject a proposal while triaging search_suggestions results. The pull request is closed on GitHub or GitLab first, so a suggestion whose host refuses the close stays open and the call reports why. Closing cannot be undone from here, and a suggestion that already merged is refused rather than closed. Use request_changes instead when the proposal is worth keeping but needs rework. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#close_suggestion
List the doc collections Promptless maintains for this organization, with the id to pass as doc_collection_id when submitting a task. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#list_doc_collections
Follow a Promptless task: wait up to 30 seconds for new messages, changed results, or completion. Omit cursor for an immediate initial snapshot; reuse the returned cursor to receive later messages. A timeout is normal: use next_call to continue waiting without a separate sleep. Drain has_more_messages even when finished is true. Read resolution and suggestions for the outcome. Use get_task_status for a one-time check. Waiting does not cancel cloud work. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#wait_for_task_update
Check the state of any documentation task in this organization and read the suggestions it produced. It covers tasks you submitted here and tasks that started in Slack, GitHub, or the Promptless dashboard. A finished task can legitimately produce nothing, so read resolution and the suggestions list rather than assuming a pull request exists. This call returns one status snapshot; finished indicates completion, and suggestions can appear while work continues. Each response includes the latest 100 conversation messages, oldest first. Track message IDs to relay new Dispatch messages once, including messages in the final response. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#get_task_status
Send additional customer instructions to an existing task submitted through the API, MCP, or the dashboard's New Task page, without creating another task. Other sources return unsupported_task_source. Only received or processing tasks accept messages. Finished tasks, including blockers and clarification requests, return task_finished and are not reopened. Reuse an idempotency_key when retrying the same message during active work. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#send_task_message
List this organization's recent documentation tasks, newest first, each with the trigger_event_id needed to check it. Use it when a task id was not kept, or to see what Promptless has been working on. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#list_recent_tasks
Search this organization's documentation suggestions by keyword, review status, and label. Use it to check whether a suggestion for a change already exists before submitting a new task, to find a suggestion id to request changes on, to pull a labelled queue such as the P0 suggestions, or to review past suggestions. Results are capped; when truncated is true, narrow the query. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#search_suggestions
Answer one completed task's marked clarification. Omit answer to ask the user through native input. Supply answer only when the user already provided it; never invent an answer. Acceptance creates a new task. Decline or cancel stops following. If native input is unavailable, ask in chat and call again with the user's answer. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/#answer_task_question
Report this Promptless organization's name, whether a person has claimed it, when an unclaimed agent-created organization expires, which integrations are connected, and the next setup steps. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/
Create a link that lets a person connect one integration to this organization in their browser. Send connect_url to someone who administers that tool. They sign in to Promptless and must be a member of this organization; the first person to open a link for an unclaimed organization claims it and becomes its owner. Call get_account_status after they finish to confirm the connection. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/
Report a Promptless problem or ask the Promptless team for help. Include relevant task or suggestion IDs in concern. Sends a one-way report; no reply comes back through this tool. Do not wait for a reply. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/
List the files in a doc collection's repository, inside the paths Promptless maintains, at the collection's default branch or at a suggestion's branch. Use it to find a page's path before reading or editing it. Results are sorted and capped; when truncated is true, narrow with path_prefix. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/
Read one file's text from a doc collection at its default branch, or at a suggestion's branch to see the proposed version. The path must lie inside the collection's maintained paths. Files over 256 KB and binary files are refused. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/
Find lines matching a substring or an RE2 regular expression (syntax similar to grep -E) across a doc collection's text files (Markdown, MDX, reStructuredText, YAML, JSON, HTML, and similar), at the default branch or at a suggestion's branch. Each match carries the file path, line number, and line text. Use it to find every page that mentions a feature, flag, or endpoint before changing it. The scan reads at most 400 files within a time budget; files_skipped reports how many were left unread, and truncated reports that more lines matched than were returned. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/
Show what a suggestion changes: one unified diff per file against the collection's base branch, plus the head commit to pass as expected_head_sha when editing. Use it to review a suggestion before labelling, editing, or opening its pull request. Diff text is capped in total; when truncated is true, later files carry no diff text. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/
Create or replace one file on an open suggestion's branch with the full content given, as one commit attributed to you. Use it for a new page or a rewrite; use edit_documentation_file for changes to part of a page. The path must lie inside the collection's maintained paths. Open the pull request with update_suggestion afterwards. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/
Replace exact text in one file on an open suggestion's branch, as one commit attributed to you. Each edit's old_text must occur exactly once in the file, so include enough surrounding lines to make it unique; the call is refused, with the match count, when it does not. Edits apply in order. Read the file first so old_text matches it verbatim. Documentation: https://promptless.ai/docs/for-docs/connect/triggers/mcp/
One endpoint, the same key, whichever client you use.
~/Library/Application Support/Claude/claude_desktop_config.json (Mac) · %APPDATA%\Claude\claude_desktop_config.json (Windows)
Replace API_KEY with your own key.
Already have an "mcpServers" section in your config? Just add the server entry inside it.
Any agentOne Gateway
Discovery, routing, credentials, tool scoping and execution logs all happen at the gateway→connections stay ACTIVE with no work from you
Promptless MCP runs through a gateway that holds the credentials, scopes the access and records every call.
Managed auth, hosted MCP servers, and every Promptless MCP tool your agent needs.
Free to start.
