Connect an app with MCP
Run your workspace from Claude, ChatGPT, Codex or any app that speaks MCP. What it can do, what waits for your approval, and what stays in bynh.
5 min readUpdated
bynh runs an MCP server at https://api.bynh.io/mcp. Connect an app to it and the app can read and work on your trust center, certificates, evidence, policies, subprocessors, status page, disclosure program, access requests and questionnaires. It has 112 tools; the MCP tool reference lists every one.
Connect an app
Step 1: Copy the address
The address is
https://api.bynh.io/mcp. You’ll also find it, with setup steps for each app, in Settings › Connected apps.Step 2: Add it to your app
In Claude, open Settings › Connectors › Add custom connector and paste the address. In ChatGPT, add a custom connector in Settings. Claude Code and Codex add it from a terminal (below). Any app that supports remote MCP servers over HTTP with OAuth works the same way: it registers itself and asks you to sign in.
Step 3: Sign in and choose what it can do
Sign in to bynh, pick the workspace, and decide whether to allow Make changes as you. Leave it off for read-only access. Viewers can only connect read only.
Step 4: Start with get_workspace
Ask the app what needs attention. It calls
get_workspacefirst, which says which workspace it works in, your role, and whether this connection may make changes right now.
claude mcp add --transport http bynh https://api.bynh.io/mcpAccess lasts until someone disconnects the app in Settings › Connected apps. You see the apps you connected; owners and admins see every app connected to the workspace.
Read only, or read and write
| Scope | What the app can do |
|---|---|
bynh:read | Read everything your role can read. Every tool that changes something answers that the connection is read-only. |
bynh:write | Also make changes, within your role. Granted when you allow Make changes as you. Anything public, emailed or destructive still waits for approval. |
Roles decide the rest. Viewers read. Editors make changes and leave requests. Some things need an owner or admin, such as the audit log, framework choices, integrations, resolving reports and the deletions that wait for approval. The tool reference gives the role for each tool.
What waits for your approval
Anything public, anything emailed to people outside your team, and anything destructive only creates a request. The app gets the status waiting_for_approval and a link, and nothing has changed yet. A person opens Settings › Connected apps and approves or declines it within 24 hours.
- Public: publishing or discarding the trust center draft, translations and new languages, showing, changing, hiding or renaming what visitors see (certificates, documents, evidence, policies, subprocessors), posting, editing or deleting incidents and maintenance, and showing monitors on the status page.
- Emailed outside your team: replies, status changes and resolutions sent to a researcher, approving, declining, resending or revoking an access request, adding a status subscriber, and inviting members.
- Destructive or leaving bynh: deleting evidence items, monitors, draft incidents, subprocessors and questionnaires, re-sending an integration delivery, and creating an issue in a connected tracker.
Before approving, the person sees exactly what will happen:
- The exact text that will be published or emailed.
- Each field that changes, old → new.
- Who gets emailed: the researcher or requester by address, or how many subscribers, followers or invitees.
- Times and affected components, for maintenance and incidents.
Approving runs the change as the person who approves, with their role, so publishing a policy or resolving a report still needs an owner or admin. Drafts, internal notes, evidence, questionnaire answers and other changes only your team sees happen at once. The app can follow its requests with list_pending_confirmations.
Attach files
There are two ways to send a file. Either way bynh checks the name, type, size and first bytes, then runs the same checks as the app.
| Way | Size | How |
|---|---|---|
| Inline | Up to 2 MB | attach_small_file takes the file base64-encoded and attaches it in the same call. |
| Upload | Larger files | start_upload returns an upload_id and a presigned URL. PUT the bytes to it (the URL works for an hour; files over 100 MB get one URL per 16 MB part), then call attach_upload within 2 hours. |
| Target | Where it goes | Types and size |
|---|---|---|
evidence | A file on an evidence item. Internal, so it attaches at once. | PDF, PNG, JPG, CSV, TXT, LOG, JSON, XLSX up to 20 MB; MP4, WebM up to 200 MB |
certificate | A certificate’s PDF. Waits for approval when the certificate is on the trust center. | PDF up to 20 MB |
document | A new version of a document. Waits for approval when visitors can see it. | As evidence |
questionnaire | A new questionnaire from the file. Nothing is sent to anyone. | XLSX, CSV, TXT, PDF up to 10 MB |
report_reply | A message on a disclosure report. A note attaches at once; a reply to the researcher waits for approval. | PNG, PDF, TXT up to 10 MB; MP4, WebM up to 200 MB |
Exports
export_evidence, export_questionnaire and read_audit_log with export return a signed download link that works for 15 minutes, plus the CSV itself when it’s small. Anyone with the link can open the file, so share it only with the person who asked. Every export is recorded in the audit log.
What stays in bynh
These are never available through MCP. An app that’s asked for them says so and points you to the bynh app:
- Billing and plans.
- Deleting the workspace or your account.
- API tokens and integration secrets.
- Connecting integrations.
- Single sign-on and domains.
- Roles, removing members and transferring ownership.
- Sessions and your profile.
- Approving or declining requests from connected apps.
- Disconnecting apps.
Limits
| Limit | Value |
|---|---|
| Calls per connected app | 120 a minute |
| Calls per person, across all their apps | 300 a minute |
| Changes per connected app | 30 a minute |
| Time to approve a request | 24 hours |
| Export links | 15 minutes |
Calls refused for their arguments don’t count towards the change limit. When a limit is reached, the tool says how many seconds to wait.
Text from outside your company
Disclosure reports, access requests, questionnaires and visitor questions come from people outside your company. bynh tells connected apps to treat that text as data, never as instructions, and anything it could trigger outside your team still waits for your approval.
Next: the MCP tool reference.
Was this helpful?