execute_custom_workflow — Linked API MCP Tool Mutating
execute_custom_workflow
(execute custom workflow) is one of 68 tools on the
Linked API
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call execute_custom_workflow from your client
- Claude Code Linked API execute_custom_workflow run in your project directory
- Claude Desktop Linked API execute_custom_workflow ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Linked API execute_custom_workflow ~/.cursor/mcp.json
- VS Code Linked API execute_custom_workflow .vscode/mcp.json
- Zed Linked API execute_custom_workflow ~/.config/zed/settings.json
- Windsurf Linked API execute_custom_workflow ~/.codeium/windsurf/mcp_config.json
- Cline Linked API execute_custom_workflow ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Linked API execute_custom_workflow ~/.gemini/settings.json
- Grok Linked API execute_custom_workflow .mcp.json (in your project root)
- ChatGPT Linked API execute_custom_workflow Settings → Connectors → Advanced → Developer mode
- Claude.ai Linked API execute_custom_workflow Settings → Connectors → Add custom connector
- LangChain Linked API execute_custom_workflow pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http linkedapi-mcp https://mcp.linkedapi.io/mcpOther tools on this server
- send_message
- sync_inbox
- get_inbox
- sync_conversation
- get_conversation
- sync_network
- get_network
- manage_conversation
- check_connection_status
- retrieve_connections
- send_connection_request
- withdraw_connection_request
- retrieve_pending_requests
- retrieve_invitations
- accept_invitation
- ignore_invitation
- remove_connection
- search_companies
- search_people
- search_jobs
- search_posts
- fetch_company
- fetch_person
- endorse_person_skill
- endorse_person_skills
- fetch_post
- fetch_job
- react_to_post
- comment_on_post
- react_to_comment
- reply_to_comment
- create_post
- create_repost
- retrieve_feed
- retrieve_profile_viewers
- retrieve_ssi
- retrieve_performance
- nv_send_message
- nv_sync_inbox
- nv_sync_conversation
- nv_get_conversation
- nv_manage_conversation
- nv_search_companies
- nv_search_people
- nv_fetch_company
- nv_fetch_person
- get_workflow_result
- get_api_usage
- send_feedback
- admin_get_subscription_status
- admin_get_seats
- admin_set_seats
- admin_get_accounts
- admin_reparse_account_info
- admin_create_reconnection_session
- admin_connect_account
- admin_get_connection_session
- admin_cancel_connection_session
- admin_disconnect_account
- admin_regenerate_token
- admin_get_limits_defaults
- admin_get_limits
- admin_get_limits_usage
- admin_set_limits
- admin_delete_limits
- admin_reset_limits
- get_changelog
This list was read from the server itself, by connecting to it and calling tools/list on 29 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.