Montra

Show your agent what to change

Category: Developer Tools
Primary Subcategory: AI Product Spec & Build Planning

Integration details

Description

Montra turns screenshots and screen recordings into agent ready tasks with the right visual context attached. Share them with your team, send them to tools like ChatGPT and Codex, or automatically create tickets in your issue tracker of choice in a few clicks.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Developer Tools
Primary Subcategory: AI Product Spec & Build Planning
Secondary Subcategories: None listed
Brand: Montra
Access: Account required
First tracked: 2026-09-13
Tool count: 15
Geography: US

ChatGPT Plugin Discovery Score

ChatGPT Plugin discovery is coming soon

ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.

No spam. Unsubscribe any time.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competing in ChatGPT AI Product Spec & Build Planning

View Category

Listed in alphabetical order

Primary Subcategory

Acceptance Criteria ExtractorComing soonGet notified

AI Task Brief BuilderComing soonGet notified

airfocusComing soonGet notified

FilmstartsComing soonGet notified

Idea To Prototype BetaComing soonGet notified

MontraComing soonGet notified

Tools

15 tools agents can invoke

Create a draft Montra document in the connected workspace. Only call this when the user explicitly asks for a new document in this conversation — never on your own initiative.
create_document
Add a ticket to a Montra document. Only call this when the user explicitly asks you to add a ticket in this conversation — never on your own initiative, e.g. to break work down or log follow-ups. `body` is the ticket's markdown implementation spec; `summary` is the one-line gist shown next to the title.
create_ticket
Remove a ticket from its Montra document. Only call this when the user explicitly asks you to delete that ticket — never to clean up work you consider finished, duplicated, or out of scope. The row is soft-deleted, so it stops appearing in the document but stays recoverable from the app.
delete_ticket
Show which Montra workspace this connection is bound to.
get_workspace
Read one Montra document with its folder, its tickets (each ticket body is the markdown implementation spec), and the status of its latest generation.
get_document
Read one Montra ticket in full, including `body` — its markdown implementation spec. Document and ticket lists omit `body`, so fetch the ticket here before implementing it.
get_ticket
Get the screenshots attached to a Montra ticket — real UI captures the person marked up while recording, so read them as part of the spec rather than as decoration. Each `url` is a short-lived signed link; fetch the images while you are working the ticket instead of storing the URLs.
get_ticket_images
Read what the person said while recording, as the narration behind a document's tickets. Pass either a documentId for every transcribed input on the document, or a single inputId. This is supporting context: the tickets remain the spec.
get_transcript
Record where a Montra ticket now lives downstream — e.g. the Linear issue you just created from it — so the ticket shows a link back. Whenever the user asks you to create an external issue from a ticket, record it here as part of that export — no separate ask is needed. Do not call it for issues you did not create, and it is not a way to mark a ticket done. One link per ticket and provider; linking again re-points the existing one.
link_ticket_issue
List recent Montra documents in the connected workspace, optionally limited to one folder.
list_documents
List the folders in the connected workspace. Use a folder id to narrow list_documents.
list_folders
Resolve a pasted Montra share link (montra.com/share/<token> or /tasks-for-agents/<token>) into its full machine-readable payload — document, tickets with markdown specs, annotated screenshot URLs, recordings, and agent instructions. Always use this instead of fetching or browsing the share web page. Works on any workspace, and on invite-only links too: when the link is not publicly readable it resolves as the Montra user who authorized this connection.
get_document_by_share_url
Semantic search across the connected workspace's documents, tickets, transcripts, inputs, analyses, and folders. Hits are resolved to the real entity they belong to: each result is a ticket, document, or folder with its own title and verbatim body text. Results are ranked by relevance and limited to what the connected user can access.
search_workspace
Replace the title and/or summary of a Montra document. Only call this when the user explicitly asks you to change them in this conversation — never on your own initiative, and never to note progress. Overwrites the stored values, including edits made by people.
update_document
Replace a Montra ticket's title, summary, or markdown body. Only call this when the user explicitly asks you to change the ticket's text in this conversation — never on your own initiative, and never to record progress (e.g. adding 'implemented', 'done', or '✅' to the title or body). The ticket is the person's spec; report progress in conversation instead. Each field you pass overwrites the stored value outright, so send the complete new text rather than a fragment or a diff.
update_ticket

Montra FAQ

How do I improve a ChatGPT Plugin's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Montra alternatives on ChatGPT?

As of 2026-09-13, Montra competes with Acceptance Criteria Extractor, AI Task Brief Builder, airfocus, Filmstarts, Idea To Prototype Beta, MVP Adviser, PeopleRun AI v.2, RuleFoundry, Zentrik in ChatGPT AI Product Spec & Build Planning, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.