
FeelingSurf
fr.feelingsurfv1.0.0Updated Oct 6, 2026
Manage your FeelingSurf traffic exchange account: sites, targeting, templates, sources and proxies.
Overview
AI-generated overview
Lets an assistant manage a FeelingSurf traffic exchange account: sites, targeting, templates, sources and proxies.
- What it does
- This remote MCP server connects an assistant to a FeelingSurf traffic exchange account. According to the registry description, it covers management of sites, targeting, templates, sources and proxies. The manifest does not list individual tools, so the exact operations available are not documented here.
- When to use it
- Worth adding if you run campaigns on the FeelingSurf traffic exchange and want an assistant to help manage account objects such as sites, targeting rules, templates, sources and proxies from a chat session.
- Requirements
- A remote streamable HTTP endpoint at An API key is required for authenticated use, sent as the Authorization header in the form Bearer , obtained from Settings then API. Listing the tools works without the key.
Before you install
The server requires an API key passed in the Authorization header; treat it as a secret and avoid exposing it in logs or shared transcripts. The description mentions managing sites, targeting, templates, sources and proxies, which may include changes to a live account, so review any write or delete action before it runs.
Installation
In SourceWeft
- Open FeelingSurf in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"feelingsurf": {
"type": "http",
"url": "https://api.feelingsurf.fr/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 6, 2026
