RD Station

RD Station Marketing, contacts/leads (get, upsert, funnel), conversion events and webhooks via the o

От сообщества: Добавлен пользователем или импортирован; проверьте владельца перед подключениемРаботаетБез входаГлобальныйБесплатноТолько чтение

Что умеет

    Какие данные видит

    Нужен ли аккаунт

    Не нужен: сервер работает без входа

    RD Station Marketing, contacts/leads (get, upsert, funnel), conversion events and webhooks via the o

    Список инструментов сервера (15)

    Технические названия из tools/list. Нужны только разработчикам.

    rdstation_list_accountsLista as contas RD Station vinculadas a este install (account_id, label).
    rdstation_account_infoDados da conta RD Station ativa (nome da conta).
    rdstation_contacts_getContatos (leads) na RD Station Marketing. Ações: - get: busca UM contato por email ou uuid. - upsert: cria/atualiza um contato (passe 'fields' com os campos do contato). - funnel: estágio do contato no funil padrão. Identifique o contato por identifier_type ('email' | 'uuid') + identifier. [Flattened action: get]
    rdstation_contacts_upsertContatos (leads) na RD Station Marketing. Ações: - get: busca UM contato por email ou uuid. - upsert: cria/atualiza um contato (passe 'fields' com os campos do contato). - funnel: estágio do contato no funil padrão. Identifique o contato por identifier_type ('email' | 'uuid') + identifier. [Flattened action: upsert]
    rdstation_contacts_funnelContatos (leads) na RD Station Marketing. Ações: - get: busca UM contato por email ou uuid. - upsert: cria/atualiza um contato (passe 'fields' com os campos do contato). - funnel: estágio do contato no funil padrão. Identifique o contato por identifier_type ('email' | 'uuid') + identifier. [Flattened action: funnel]
    rdstation_eventsCria um evento de conversão na RD Station Marketing (POST /platform/events). Passe 'event' com o payload completo (event_type, event_family, payload com email, etc.).
    rdstation_webhooks_listWebhooks da RD Station Marketing. Ações: - list: lista webhooks configurados. - create: cria um webhook (passe 'webhook' com url, event_type, entity_type…). - delete: remove um webhook (requer uuid). [Flattened action: list]
    rdstation_webhooks_createWebhooks da RD Station Marketing. Ações: - list: lista webhooks configurados. - create: cria um webhook (passe 'webhook' com url, event_type, entity_type…). - delete: remove um webhook (requer uuid). [Flattened action: create]
    rdstation_webhooks_deleteWebhooks da RD Station Marketing. Ações: - list: lista webhooks configurados. - create: cria um webhook (passe 'webhook' com url, event_type, entity_type…). - delete: remove um webhook (requer uuid). [Flattened action: delete]
    show_versionShow the current MCP platform and adapter versions.
    report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
    connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
    toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
    marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
    authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.