paperclipai/paperclip-docs

0 Fork 0

mirror of https://github.com/paperclipai/paperclip-docs.git synced 2026-11-07 06:16:07 -10:00

Files

T

39633c2217 docs: connectors catalog, operator-first third revision (#124 )

Connector catalog, setup guides, and shared access documentation,
followed by a final code-accuracy repair pass. This PR does not change
application behavior.

## Final accuracy pass

Checked against shipped Paperclip `v2026.916.0`, commit
`dffc2b3ca1b9e88fa21cb17493083e682dffd1ca`, rather than the dirty local
checkout or the earlier canary baseline.

- Corrects connector/method-specific identity choices, human audiences,
and managed GitHub versus PAT scope and verification.
- Explains that **Always allow** covers different arguments for the same
agent/action/connection, with project scope when present; uses actual
button labels and removes the test-panel control from review
instructions.
- Qualifies new-action quarantine, including safe-default read
exceptions. Removes unconditional approval guarantees.
- Separates provider channel/repository reach from Paperclip sender
authorization.
- Completes sandbox sign-in and model credential-selection instructions
from the current UI implementation.
- Repairs Notion's hub summary, removes incomplete optional
Notion/Sentry client-registration procedures, and corrects Linear's
provider-versus-Paperclip attribution.
- Removes unsupported Postman tier claims, contradictory Cloudinary/Mem0
verification assertions, API-equivalence claims, and overbroad
successful-test assurances.
- Retains Supabase's required project reference: both released method
definitions explicitly require it. An earlier review suggested
otherwise; release code is authoritative here.
- Updates the release baseline and removes draft commit chronology from
the public introduction.

## Availability and remaining runtime gates

- **Google:** Verification is pending. Per the product-owner
clarification, authorization can continue where Google offers an
Advanced option; this is not available for every account and does not
override Workspace policy or other Google prerequisites. Notices on the
hub and all Google guides now distinguish an unverified-app warning from
blocked authorization.
- **Slack is available but not yet fully functional; follow-up fixes are
planned.** For agent tools, the released OAuth endpoint/scope defaults
differ from Slack's documented MCP contract. The page now warns against
treating that route as production-ready and removes the misleading
bot-scope walkthrough. Chat-channel bot setup remains separate.
Engineering must reconcile the integration and run OAuth plus one read
before removing this warning. Source:
https://docs.slack.dev/ai/slack-mcp-server/
- No credentialed connector run was performed in this pass. Code
consistency, provider documentation, UI rendering, and successful live
execution are separate evidence levels. No claim of runtime
certification for all connectors.

## Validation

- Root build: 253 crawlable documentation pages.
- Full `docs:test`: all eight suites passed locally, including
root/subpath routes, sitemap history, fingerprints, navigation, skill
source blocks, crawlable links, doc-link resolution, and SEO metadata.
- Internal-link lint: 258 Markdown files; no broken internal links.
- Latest cleanup: full build, all eight docs:test suites, internal-link
lint and diff whitespace checks passed; 1,878 link-resolution checks.
- Fixed the Calendar MCP reference URL; browser-checked the five
inconclusive external destinations (Miro article loads; Asana, Google
Cloud, OpenAI and xAI reach sign-in/console screens). Authenticated
destinations were not tested beyond those screens.
- Replaced the Sandbox providers editorial TODO with a scope note and
removed the CLI overview's unfinished-guide announcement.
- Browser client navigation: 687 checks passed using installed Chrome.
Initial launch lacked the downloaded Playwright browser; rerun used
`DOCS_CHROMIUM_PATH` without changing the tests.
- Nine representative connector/shared pages at 1440px and 390px: HTTP
200, one article H1, no page-level horizontal overflow. Mobile
screenshot inspected; approval page opened in the Codex browser.
- Navigation audit reports three existing non-connector orphan files;
this patch does not alter those files or their navigation.

The previous revision's provider-page expansion, Google shared setup
guide, navigation additions, and accidental node_modules-symlink cleanup
remain in this PR. Internal review ledgers remain outside the
publication branch. No merge or production deployment authorized.

---------

Co-authored-by: DevRel Gemini <[email protected]>
Co-authored-by: Paperclip <[email protected]>
Co-authored-by: Claude Opus 5 (1M context) <[email protected]>
Co-authored-by: Michael Nguyen <[email protected]>

2026-09-16 22:19:14 -10:00

3.8 KiB

Raw Blame History

seo_title, seo_description

seo_title	seo_description
Miro Connector	Let agents read and update Miro boards. Team and board reach, what board objects are actually available, a read test, and troubleshooting.

Miro

Agents can work with your Miro boards — finding them, reading their contents, and adding or updating items.

Before you connect

A Miro account with access to the teams and boards you want agents to use.
On enterprise plans, an administrator may restrict which third-party MCP clients are allowed. If authorization is refused, that is the usual cause.

Connect Miro

Open Connectors and select Miro.
On the Access step, choose the identity and which agents may use the connection.
Select Sign in with Miro and complete browser sign-in, choosing the team when Miro asks.

Paperclip registers its client automatically, so there is nothing to configure in a developer console.

Choose access

Reach is the authorizing Miro account's: the teams it belongs to and the boards it can open. There is no board picker in Paperclip.

Be realistic about what an agent can do with a board. Miro's connection works with structured board objects rather than the canvas as a person experiences it. Which object types are exposed is Miro's decision and it changes — read the live list on the connection's Permissions tab before planning work around a particular item type, rather than trusting any list in documentation, including this page:

An agent reads objects and their content and position. It does not "see" the board the way a person does, so spatial meaning conveyed only by layout may be lost.
Freehand drawings, embedded content, and interactive widgets are not equivalent to structured items.
Anything an agent adds will be placed programmatically, and will need a person to tidy it if placement matters.

Writes land on a board colleagues may be using at that moment. Keep them on Ask first while you learn how the agent behaves. See Set action permissions.

Try it

Identify the board by its URL rather than its name, and check the result against a board you can open:

Read this Miro board — https://miro.com/app/board/YOUR_BOARD_ID/ — and list the
sticky notes grouped by their frame. Do not add or move anything.

Compare against the board. Reading a board you can open yourself confirms the credential, the team, and the agent's permission without rearranging anyone's work.

Note: Illustrative task, not a recorded test result. Substitute a board name from your own team.

Troubleshooting and limitations

Problem	Likely cause	Fix
Authorization is refused	An enterprise administrator restricts third-party MCP clients	Ask a Miro administrator to allow it
A board is not found	The authorizing account cannot open it, or it belongs to another team	Share the board, or reconnect selecting the right team
Board content seems incomplete	Freehand, embedded, or widget content is not structured board objects	Expected; those are not exposed as items
The agent misunderstood the board's layout	Meaning conveyed by spatial arrangement is not carried by the object data	Give the agent explicit context rather than relying on layout
An item appeared in an odd place	Programmatic placement	Move it in Miro, and keep writes on Ask first
Needs attention	The grant was revoked	Select Reconnect

Limitations: one Miro account per connection. No board filter inside Paperclip. Structured board objects only.

3.8 KiB Raw Blame History