MCP App Store
by KeenEthics
Developer-Tools

Sinch Build Docs

by Sinch

Overview

Search and explore Sinch Build developer documentation directly from Claude. This connector lets you find relevant content across the docs, list the available Sinch APIs, and inspect individual endpoints, including their parameters, examples, and security requirements. You can also pull full OpenAPI descriptions and security schemes for any API. Because it is read-only and needs no authentication, it is fast and safe to use for everyday research. Whether you are integrating SMS, RCS, voice, verification, numbers, or email, the Sinch Docs connector helps you quickly find accurate, up-to-date answers and the exact reference details you need to build.

Tools

describe-tools

Claude
Get the exact TypeScript signatures of the sandbox tools available to execute. Analyze the user request first, then pass tools with only the tool names the request needs (every name is listed in this input schema / description); omit tools only when you cannot tell which tools apply. Always call this before your first execute and never guess signatures. Request every tool the task may need in ONE call instead of calling this repeatedly.

execute

Claude
Run JavaScript in a sandbox against the documentation tools on the global tools object. The only extra global is tools - there is no fetch, console, setTimeout, require, or Node.js API; all I/O goes through tools. Workflow - minimize round-trips; one describe-tools call plus one execute call covers most requests: 1. Analyze the request and decide which sandbox tools it needs (every tool name is listed in the describe-tools input schema / description). 2. Call describe-tools with those names to get their exact TypeScript signatures - inputs AND result shapes. NEVER call execute with guessed method names, parameter names, enum values, or result field names: read fields off the declared return types, not from assumptions. 3. Batch everything into a SINGLE script: chain tool calls, pass one call's output into the next, process results in plain JavaScript, and return only what the request needs. Example - list the write endpoints of an API: ``ts const { items } = await tools.listApis({ filter: 'billing' }); const { endpoints } = await tools.getEndpoints({ name: items[0].name }); const writes = endpoints.filter((e) => e.method !== 'GET'); return { api: items[0].name, writes: writes.map((e) => ${e.method} ${e.path}) }; ``

get-endpoint-info

Claude

get-endpoints

Claude

get-full-api-description

Claude

get-security-schemes

Claude

list-apis

Claude

App Stats

8

Tools

Claude

Platforms

Works with

Claude

Data refreshed daily