> ## Documentation Index > Fetch the complete documentation index at: https://docs.anny.co/llms.txt > Use this file to discover all available pages before exploring further. # Get MCP registry config > Returns the MCP connection bootstrap config for the active organization and requested registry. For the `customer` registry this includes organization-specific prompts, the MCP transport URL, and the tenant header that must be sent on subsequent MCP requests. Use this endpoint first, then connect to the returned `mcp_url` and call `initialize` followed by `tools/list` over MCP JSON-RPC. ## OpenAPI ````yaml /developers/openapi/admin-internal.openapi.json get /mcp/{registry}/config openapi: 3.1.0 info: title: admin-api version: '1.0' description: >- The Admin API gives you **full programmatic access** to your anny organization. It is built for **server-side integrations** — backend services, automation scripts, and custom tooling that act on behalf of your team. --- ## When to use the Admin API Use the Admin API when you need to **drive workflows from your own systems**: - **Sync membership data** — create or update customers, assign them to communities, reflect subscription status from an external CRM - **Create bookings programmatically** — build back-office tools or automate repeat reservations without going through the customer checkout - **Issue and forward invoices** — generate invoices, send them to customers, or push them to your accounting system - **React to real-time events** — pair the API with [Webhooks](/developers/guides/admin/webhooks) to trigger side effects whenever a booking is created, cancelled, or checked in - **Drive display panels** — push live occupancy and schedule data to digital signage or lobby displays Combined with [webhook subscriptions](/developers/guides/admin/webhooks), you can build fully automated, event-driven workflows without polling. --- ## Authentication Generate a long-lived API token directly in the admin dashboard under **Organization Settings → API**. All requests require it in the `Authorization` header: ``` Authorization: Bearer {access_token} ``` Every endpoint is **organization-scoped**. Pass your organization ID as a query parameter on every request: ``` ?o={organization_id} ``` See the [Authentication guide](/developers/guides/authentication) for token scopes and the full OAuth2 flow. --- ## Admin API vs Customer API | | Admin API | Customer API | |---|---|---| | **Use case** | Server-side automation, backend tooling | End-user apps, booking widgets | | **Auth** | Required — API token or OAuth2 | Optional — many endpoints work without a token | | **Identifiers** | Immutable UUIDs and integer IDs | Slugs, booking numbers, order numbers | | **Access** | Full read/write | Public and customer-owned data only | → [Go to the Customer API](/developers/api-reference/customer) --- ## Resource Identifiers The Admin API uses **immutable IDs** — UUIDs for most entities, integers for legacy ones. These are safe to store in external systems and never change, even if an organization renames a resource. --- ## Starting Points | Guide | What it covers | |---|---| | [Getting Started](/developers) | First steps and quickstart | | [JSON:API Conventions](/developers/guides/json-api-conventions) | Request and response format | | [Authentication](/developers/guides/authentication) | API tokens, OAuth2, scopes | | [Availability & Booking Search](/developers/guides/availability) | Search open slots and timeslots | | [Admin Booking Creation](/developers/guides/admin/booking-creation) | Create bookings from the back office | | [Admin Booking Edit](/developers/guides/admin/booking-edit) | Edit resource, dates, fields, add-ons, and sub-bookings | | [Admin Booking Lifecycle](/developers/guides/admin/booking-lifecycle) | Status changes, check-in, cancellations | | [Invoices](/developers/guides/admin/invoices) | Create, send, and manage invoices | | [Customer Management](/developers/guides/admin/customer-management) | Create and manage customer records | | [Booking Calendars](/developers/guides/admin/calendar-events) | Custom calendar events | | [Timeslot Management](/developers/guides/admin/timeslot-management) | Manage timeslot CRUD, recurrence, allocations, and rescheduling | | [Broadcast Campaigns](/developers/guides/admin/broadcasting) | Email and push campaigns | | [Exports](/developers/guides/admin/exports) | Export bookings and customer data | | [Webhooks & Events](/developers/guides/admin/webhooks) | Subscribe to real-time events | --- ## Base URLs | Environment | URL | |---|---| | Production | `https://b.anny.co` | | Gov-Cloud | `https://b.anny.eu` | contact: name: anny GmbH url: https://anny.co email: support@anny.co servers: - url: https://b.anny.co description: Production - url: https://b.anny.eu description: Gov-Cloud security: - Bearer: [] tags: - name: Booking Quotas - name: Orders - name: Organizations - name: Table Configuration - name: Test-Results - name: User Settings - name: Terminal Locations - name: Terminal Readers - name: Connection Tokens - name: Views - name: Voice Integration paths: /mcp/{registry}/config: parameters: - schema: type: string enum: - customer name: registry in: path required: true description: >- MCP registry alias. Currently only `customer` is documented for external client setup. get: tags: - Organizations summary: Get MCP registry config description: >- Returns the MCP connection bootstrap config for the active organization and requested registry. For the `customer` registry this includes organization-specific prompts, the MCP transport URL, and the tenant header that must be sent on subsequent MCP requests. Use this endpoint first, then connect to the returned `mcp_url` and call `initialize` followed by `tools/list` over MCP JSON-RPC. operationId: get-mcp-registry-config parameters: - $ref: '#/components/parameters/organizationId' responses: '200': description: OK content: application/json: schema: type: object additionalProperties: false properties: system_prompt: type: - string - 'null' description: >- Full organization-specific system prompt for the customer MCP agent. embedded_prompt: type: - string - 'null' description: >- Shorter embedded prompt variant for hosts that inject instructions separately. prompts: type: array description: >- Reserved prompt list for future registry-specific prompt variants. items: type: object additionalProperties: true tenant_id: type: - string - 'null' description: >- Organization external ID to send as `X-Tenant-ID` on MCP requests. mcp_url: type: string format: uri description: Streamable HTTP MCP endpoint for the selected registry. example: https://b.anny.co/mcp/customer mcp_headers: type: object additionalProperties: type: string description: Headers that must be included when talking to `mcp_url`. example: X-Tenant-ID: 550e8400-e29b-41d4-a716-446655440000 '401': description: Unauthorized '404': description: Registry not found security: - Bearer: [] components: parameters: organizationId: name: o in: query description: Organization ID. Required for multi-tenant scoping. schema: type: string securitySchemes: Bearer: type: oauth2 flows: authorizationCode: authorizationUrl: https://auth.anny.co/oauth/authorize tokenUrl: https://auth.anny.co/oauth/token refreshUrl: https://auth.anny.co/oauth/token/refresh scopes: {} ````