Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Beeceptor (BYOK) icon

Beeceptor (BYOK)

Read the mock rules, request history, settings and state store of a Beeceptor mock endpoint with that endpoint's API key

Unify Dynamics LLC

Tools8read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderBeeceptorunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What mock rules does my Beeceptor endpoint my-mock have?
Tools called
list_rules
Show Beeceptor rule 1ua4j6kb1e2 of my-mock
Tools called
get_rule
What requests did my Beeceptor endpoint my-mock receive recently?
Tools called
list_requests
Show the body of Beeceptor request r1 on my-mock
Tools called
get_request
How is my Beeceptor endpoint my-mock configured?
Tools called
get_settings
What state variables does my Beeceptor endpoint my-mock hold?
Tools called
list_state

About

Beeceptor (BYOK) lets an AI assistant read your own Beeceptor data through the Beeceptor API with a key you supply (Beeceptor endpoint API key (Team plan or higher)). Read-only: 8 tools (list_rules, get_rule, list_requests, get_request, get_settings, list_state, get_state_item, get_spec_info). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.beeceptor.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Beeceptor. Beeceptor and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Beeceptor API (api.beeceptor.com) with a BYOK key; documentation: https://beeceptor.com/docs/api/beeceptor-api/. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

8 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data8 tools
  • List rulesList the mock rules of a Beeceptor endpoint with method, description, match conditions and response action.
  • Get ruleGet one Beeceptor mock rule by id: method, conditions and response action.
  • List requestsList requests received by a Beeceptor endpoint (newest first) with method, path, status code, time taken and which rule matched.
  • Get requestGet one request received by a Beeceptor endpoint with method, path, status, matched rule and the request and response bodies.
  • Get settingsGet the settings of a Beeceptor endpoint: CORS origins, rate limit, locale, latency, proxy target and custom domain.
  • List stateList the persistent state variables (strings, counters, lists) stored by a Beeceptor endpoint, optionally by type or key prefix.
  • Get state itemGet one state variable of a Beeceptor endpoint by type and key.
  • Get spec infoGet the type of API specification (OpenAPI, gRPC, GraphQL or WSDL) uploaded to a Beeceptor endpoint and whether intelligent mocking is on.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-beeceptor.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 8 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-beeceptor.connectorbay.com/mcp
RESTPOST https://byok-beeceptor.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-beeceptor.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your Beeceptor endpoint API key (Team plan or higher) in the X-Upstream-Key header (get one at beeceptor.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Beeceptor connector: questions and answers

What is the Beeceptor connector?

Beeceptor (BYOK) lets an AI assistant read your own Beeceptor data through the Beeceptor API with a key you supply (Beeceptor endpoint API key… It is a hosted MCP server with 8 tools such as List rules, Get rule, List requests, Get request, Get settings, List state, published by Unify Dynamics LLC. It is independent and not affiliated with Beeceptor.

How do I connect Beeceptor to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-beeceptor.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-beeceptor.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-beeceptor.json.

Do I need a Beeceptor account or API key?

Yes: this is a bring-your-own-key connector. Create a Beeceptor endpoint API key (Team plan or higher) at https://beeceptor.com/docs/api-overview and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Beeceptor read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Beeceptor connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Opik Workspace Admin (BYOK)

Read the retention rules, dashboards, alerts, environments, workspace settings and workspace metric totals of your Opik workspace with your own Comet API key

Live · MCP + REST6 tools

Opsgenie (BYOK)

Read your Opsgenie alerts, incidents, on-call schedules, teams, users, escalations and heartbeats with BYOK (US region)

Live · MCP + REST10 tools

OpsLevel (BYOK)

Read your OpsLevel software catalog services, teams, systems, domains, scorecards, deploys and infrastructure with your own API token

Live · MCP + REST12 tools

Optimizely (BYOK)

Read your Optimizely Web and Feature Experimentation projects, experiments, campaigns, flags, audiences, events and environments with BYOK

Live · MCP + REST9 tools

Optimizely Project Setup (BYOK)

Read your Optimizely pages, attributes, exclusion groups, extensions, scheduled reports, experiment results and impressions usage with your own personal access token

Live · MCP + REST8 tools

OptiView Live (BYOK)

Read your OptiView Live (THEOlive) channels, ingests, engines, distributions, regions and ABR ladders with your own API token and secret

Live · MCP + REST8 tools

Documentation

Back to top

Beeceptor (BYOK) — connector documentation

  • MCP endpoint: https://byok-beeceptor.connectorbay.com/mcp
  • REST API: POST https://byok-beeceptor.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-beeceptor.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Beeceptor Beeceptor endpoint API key (Team plan or higher), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-beeceptor.connectorbay.com/health · Tool schemas: https://byok-beeceptor.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-beeceptor · agent@connectorbay.com

What Beeceptor (BYOK) is for

Beeceptor (BYOK) lets an AI assistant read your own Beeceptor data through the Beeceptor API with a key you supply (Beeceptor endpoint API key (Team plan or higher)). Read-only: 8 tools (list_rules, get_rule, list_requests, get_request, get_settings, list_state, get_state_item, get_spec_info). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.beeceptor.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Beeceptor. Beeceptor and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "What mock rules does my Beeceptor endpoint my-mock have?"
  • "Show Beeceptor rule 1ua4j6kb1e2 of my-mock"
  • "What requests did my Beeceptor endpoint my-mock receive recently?"
  • "Show the body of Beeceptor request r1 on my-mock"
  • "How is my Beeceptor endpoint my-mock configured?"
  • "What state variables does my Beeceptor endpoint my-mock hold?"

What it does

  • list_rules: List the mock rules of a Beeceptor endpoint with method, description, match conditions and response action.
  • get_rule: Get one Beeceptor mock rule by id: method, conditions and response action.
  • list_requests: List requests received by a Beeceptor endpoint (newest first) with method, path, status code, time taken and which rule matched. Bodies are not included.
  • get_request: Get one request received by a Beeceptor endpoint with method, path, status, matched rule and the request and response bodies.
  • get_settings: Get the settings of a Beeceptor endpoint: CORS origins, rate limit, locale, latency, proxy target and custom domain. The endpoint's access header value is left out.
  • list_state: List the persistent state variables (strings, counters, lists) stored by a Beeceptor endpoint, optionally by type or key prefix.
  • get_state_item: Get one state variable of a Beeceptor endpoint by type and key.
  • get_spec_info: Get the type of API specification (OpenAPI, gRPC, GraphQL or WSDL) uploaded to a Beeceptor endpoint and whether intelligent mocking is on.

BYOK key

You bring your own Beeceptor Beeceptor endpoint API key (Team plan or higher) (https://beeceptor.com/docs/api-overview). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.beeceptor.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Beeceptor API (api.beeceptor.com) with a BYOK key; documentation: https://beeceptor.com/docs/api/beeceptor-api/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Beeceptor. Beeceptor and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Beeceptor account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Beeceptor (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Beeceptor (BYOK) is. Beeceptor (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Beeceptor data: Read the mock rules, request history, settings and state store of a Beeceptor mock endpoint with that endpoint's API key. You bring your own Beeceptor Beeceptor endpoint API key (Team plan or higher); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Beeceptor call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.beeceptor.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Beeceptor rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Beeceptor receives. The request we make on your behalf, including the key and the arguments, under Beeceptor's own terms and privacy policy. Beeceptor acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Beeceptor gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Beeceptor data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Beeceptor (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Beeceptor at any time to end all access.

Children. Beeceptor (BYOK) is a general-audience service operated by the adult using the assistant, under Beeceptor's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Beeceptor (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Beeceptor (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Beeceptor (BYOK) provides: Read the mock rules, request history, settings and state store of a Beeceptor mock endpoint with that endpoint's API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Beeceptor credentials and only access data you are allowed to access. Beeceptor's terms apply to your use of Beeceptor; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Beeceptor. Beeceptor and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Beeceptor returns, lightly trimmed; it may be incomplete, delayed or changed by Beeceptor. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Beeceptor account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Beeceptor's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Beeceptor may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Beeceptor key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Beeceptor takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-beeceptor

Beeceptor (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Beeceptor (BYOK) never asks for them.

Get Beeceptor (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Beeceptor Beeceptor endpoint API key (Team plan or higher). Create one at https://beeceptor.com/docs/api-overview, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Beeceptor. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Beeceptor.