Felt (BYOK)

Felt (BYOK) — connector documentation

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

What Felt (BYOK) is for

Felt (BYOK) lets an AI assistant read your own Felt data through the Felt API with a key you supply (Felt personal access token (starts with felt_pat_)). Read-only: 11 tools (get_current_user, list_projects, get_project, get_map, list_map_layers, get_map_layer, list_map_layer_groups, list_map_elements, list_sources, get_source, list_library_layers). 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 felt.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Felt. Felt 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:

• "Which Felt account is my token connected to?"
• "Which Felt projects do I have?"
• "Which maps are in Felt project prjAb12Cd34Ef56Gh78Ij?"
• "What are the details of Felt map mCjGDq6nQz2xSp1kT3wLvA?"
• "What layers does Felt map mCjGDq6nQz2xSp1kT3wLvA have?"
• "Show details of layer lyrAb12Cd34Ef56Gh78Ij90 on Felt map mCjGDq6nQz2xSp1kT3wLvA"

What it does

• get_current_user: Show the Felt account the token belongs to: user id and name.
• list_projects: List the projects (folders for maps) in the workspace with name, visibility and the maximum inherited permission.
• get_project: Get one project with its maps (id, title, link, dates).
• get_map: Get one map's metadata: title, URL, basemap, project, public access level, thumbnail and dates. Use list_map_layers for its layers.
• list_map_layers: List the layers of a map with name, geometry type, processing status, refresh schedule and source attribution.
• get_map_layer: Get one layer of a map: name, caption, geometry type, status, refresh settings and source attribution.
• list_map_layer_groups: List the layer groups of a map (named sets of layers shown together in the legend) with the layers in each.
• list_map_elements: List the drawn annotations (markers, lines, polygons, notes) on a map as a GeoJSON feature collection.
• list_sources: List the data sources (databases, buckets, services) connected to the workspace with type, sync status and dates. Connection details are not returned.
• get_source: Get one connected data source with its sync status and the datasets it exposes. Connection details are not returned.
• list_library_layers: List the layers published in the workspace layer library or Felt's global library, with attribution and geometry type.

BYOK key

You bring your own Felt Felt personal access token (starts with felt_pat_) (https://felt.com/maps/latest/developers). 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 felt.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

• https://developers.felt.com/rest-api/api-reference (the API this connector calls, with a BYOK key)

Live from the Felt API (felt.com) with a BYOK key; documentation: https://developers.felt.com/rest-api/api-reference. 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 Felt. Felt 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 Felt account.

Built for: Worldwide. Languages: English.

Felt (BYOK) — Privacy Policy

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

What Felt (BYOK) is. Felt (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Felt data: Read the maps, layers, projects, data sources, annotations and layer library of your Felt workspace with your own personal access token. You bring your own Felt Felt personal access token (starts with felt_pat_); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Felt 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 felt.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 Felt 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 Felt receives. The request we make on your behalf, including the key and the arguments, under Felt's own terms and privacy policy (https://help.felt.com/legal/terms-of-service). Felt acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Felt 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 Felt 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. Felt (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 Felt at any time to end all access.

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

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

Felt (BYOK) — Terms of Service

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

1. The Service. Felt (BYOK) provides: Read the maps, layers, projects, data sources, annotations and layer library of your Felt workspace with your own personal access token. 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 Felt credentials and only access data you are allowed to access. Felt's terms (https://help.felt.com/legal/terms-of-service) apply to your use of Felt; 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 Felt. Felt 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 Felt returns, lightly trimmed; it may be incomplete, delayed or changed by Felt. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Felt 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 Felt'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; Felt 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 Felt 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 Felt 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-felt

Felt (BYOK) support

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

• MCP endpoint: https://byok-felt.connectorbay.com/mcp
• REST API: https://byok-felt.connectorbay.com/openapi.json
• Live status: https://byok-felt.connectorbay.com/health

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. Felt (BYOK) never asks for them.