통합 크레딧 시스템을 통해 장기 기억 기능과 100개 이상의 통합 서비스를 활용하여 AI agent가 지능적인 워크플로우를 오케스트레이션할 수 있도록 지원합니다.
다른 이름 Agentled/mcp-server, @agentled/mcp-server
- 스타
- 3
- Tools
- 107
- 다운로드, 30일
- 1,078
- 최신 버전
- 0.20.1
- 마지막 커밋
- 2026년 10월 15일
- 라이선스
- MIT
Agentled MCP란?
Agentled은(는) MCP server입니다. 통합 크레딧 시스템을 통해 장기 기억 기능과 100개 이상의 통합 서비스를 활용하여 AI agent가 지능적인 워크플로우를 오케스트레이션할 수 있도록 지원합니다. 107개 도구를 제공합니다. 예: list_workflows, get_workflow, get_workflow_credits.
프로젝트 README에서 생성된 요약
Agentled MCP server 정보
Agentled는 AI agent가 지능적인 오케스트레이션을 통해 복잡한 워크플로우를 관리할 수 있도록 설계된 자동화 엔진을 제공합니다. Claude, Cursor, Windsurf와 같은 MCP 호환 클라이언트를 단일 API key와 통합 크레딧 시스템을 사용하여 100개 이상의 통합 서비스에 연결합니다. 이 방식을 통해 LinkedIn, 이메일 서비스, 웹 스크래퍼 또는 다양한 AI 모델과 같은 도구들을 위해 별도의 구독을 관리할 필요가 없습니다.
핵심 기능은 내장된 Knowledge Graph로, 다양한 실행 과정에서 얻은 인사이트와 비즈니스 컨텍스트를 저장하여 장기 기억 역할을 수행합니다. 이를 통해 agent는 과거의 조사 결과와 성과로부터 학습하여 시간이 지남에 따라 정확도를 높일 수 있습니다. 또한 이 server는 Agent Teams를 통한 고급 협업을 지원하며, 여러 AI 전문가가 research-and-summarize 또는 analyze-and-recommend와 같은 프리셋을 사용하여 다단계 작업을 함께 수행할 수 있습니다.
개발자는 npx를 사용하여 stdio를 통해 로컬에 server를 설정하거나, Claude Code 및 Codex용 전용 플러그인을 사용할 수 있습니다. 시스템은 CRM 동기화, 미디어 제작, 웹 스크래핑을 포함한 다양한 기능을 지원하기 위해 크레딧 기반 모델을 사용합니다.
활용 사례
- 1자동화된 리드 생성agent가 특정 전문가 프로필을 찾고, 연락처 데이터를 추가하며, 이상적인 고객 프로필(ICP)을 기준으로 점수를 매길 수 있습니다.
- 2시장 및 기업 인텔리전스사용자는 agent에게 기업의 투자 유치 현황 및 시장 지위에 대한 심층 조사를 수행하여 투자 메모를 작성하도록 지시할 수 있습니다.
- 3멀티 에이전트 콘텐츠 제작개발자는 주제 스크래핑, 소셜 미디어 게시물 작성, 관련 이미지 생성을 수행하는 전문가 팀을 배포할 수 있습니다.
- 4협업형 AI 추론옵션 비교 또는 콘텐츠 검토와 같은 특정 패턴을 사용하는 전문 agent 그룹에 작업을 할당할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Agentled MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Agentled MCP 설치
$ claude mcp add --env 'AGENTLED_API_KEY=<YOUR_AGENTLED_API_KEY>' mcp-server -- npx -y @agentled/mcp-serverCursor에 Agentled MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@agentled/mcp-server"
],
"env": {
"AGENTLED_API_KEY": "<YOUR_AGENTLED_API_KEY>"
}
}
}
}VS Code에 Agentled MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agentled/mcp-server"
],
"env": {
"AGENTLED_API_KEY": "<YOUR_AGENTLED_API_KEY>"
}
}
}
}VS Code CLI에 Agentled MCP 설치
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@agentled/mcp-server"],"env":{"AGENTLED_API_KEY":"<YOUR_AGENTLED_API_KEY>"}}'Claude Desktop에 Agentled MCP 설치
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@agentled/mcp-server"
],
"env": {
"AGENTLED_API_KEY": "<YOUR_AGENTLED_API_KEY>"
}
}
}
}Codex에 Agentled MCP 설치
$ codex mcp add mcp-server --env 'AGENTLED_API_KEY=<YOUR_AGENTLED_API_KEY>' -- npx -y @agentled/mcp-serverCodex config.toml에 Agentled MCP 설치
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@agentled/mcp-server"] [mcp_servers.mcp-server.env] AGENTLED_API_KEY = "<YOUR_AGENTLED_API_KEY>"
Gemini CLI에 Agentled MCP 설치
$ gemini mcp add -s user -e 'AGENTLED_API_KEY=<YOUR_AGENTLED_API_KEY>' mcp-server npx -- -y @agentled/mcp-serverGemini settings.json에 Agentled MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@agentled/mcp-server"
],
"env": {
"AGENTLED_API_KEY": "<YOUR_AGENTLED_API_KEY>"
}
}
}
}Agentled MCP 도구 107
README에서 감지됨list_workflowsget_workflowget_workflow_creditscreate_workflowupdate_workflowupdate_workflow_contextadd_stepupdate_stepreplace_step_dictionaryreplace_step_pathunset_step_pathappend_step_array_item
| list_workflows | — | |
| get_workflow | — | |
| get_workflow_credits | — | |
| create_workflow | — | |
| update_workflow | — | |
| update_workflow_context | — | |
| add_step | — | |
| update_step | — | |
| replace_step_dictionary | — | |
| replace_step_path | — | |
| unset_step_path | — | |
| append_step_array_item | — |
도구 107개 모두 보기도구 수 줄이기
remove_step_array_itemremove_stepdelete_workflowvalidate_workflowpublish_workflowexport_workflowimport_workflowlist_public_form_linkscreate_public_form_linkupdate_public_form_linkenabledexpiresAtsubmissionLimitautoShareshareExpiresInDayssuccessMessageupdatesreplaceunsetmetadataget_draftpromote_draftdiscard_draftcreate_snapshotdelete_snapshotlist_snapshotsget_snapshot_contentrestore_snapshotstart_workflowlist_executionsget_executionlist_timelinesget_timelinestop_executionretry_executionrerunlist_appslist_connectionsverify_app_connectionget_app_actionstest_app_actiontest_ai_actiontest_code_actionget_step_schemaget_workspaceget_workspace_company_profileupdate_workspace_company_profileupdate_workspace_executive_summarylist_pinned_outputsset_output_page_pininspect_home_recent_tabconfigure_home_recent_tablist_workspace_viewscreate_workspace_viewget_workspace_viewupdate_workspace_viewarchive_workspace_viewlist_knowledge_listsget_knowledge_rowsget_knowledge_rows_by_idsget_knowledge_textcreate_knowledge_listupdate_knowledge_list_schemadelete_knowledge_listupsert_knowledge_rowsdelete_knowledge_rowsupsert_knowledge_textdelete_knowledge_textquery_kg_edgesget_scoring_historyget_workspace_creditsget_workspace_credit_cost_driversrolling-30-daysrolling-7-dayscurrentprevious-monthall-timeget_brandingupdate_brandinglist_agentsget_agentcreate_agentupdate_agentactivate_agentpause_agentmanage_agent_workflowsdelete_agentchat_with_agentlist_agent_filesget_agent_fileupload_agent_fileupdate_agent_filedelete_agent_filemessagesession_id
| remove_step_array_item | — | |
| remove_step | — | |
| delete_workflow | — | |
| validate_workflow | — | |
| publish_workflow | — | |
| export_workflow | — | |
| import_workflow | — | |
| list_public_form_links | — | |
| create_public_form_link | — | |
| update_public_form_link | — | |
| enabled | — | |
| expiresAt | — | |
| submissionLimit | — | |
| autoShare | — | |
| shareExpiresInDays | — | |
| successMessage | — | |
| updates | — | |
| replace | — | |
| unset | — | |
| metadata | — | |
| get_draft | — | |
| promote_draft | — | |
| discard_draft | — | |
| create_snapshot | — | |
| delete_snapshot | — | |
| list_snapshots | — | |
| get_snapshot_content | — | |
| restore_snapshot | — | |
| start_workflow | — | |
| list_executions | — | |
| get_execution | — | |
| list_timelines | — | |
| get_timeline | — | |
| stop_execution | — | |
| retry_execution | — | |
| rerun | — | |
| list_apps | — | |
| list_connections | — | |
| verify_app_connection | — | |
| get_app_actions | — | |
| test_app_action | — | |
| test_ai_action | — | |
| test_code_action | — | |
| get_step_schema | — | |
| get_workspace | — | |
| get_workspace_company_profile | — | |
| update_workspace_company_profile | — | |
| update_workspace_executive_summary | — | |
| list_pinned_outputs | — | |
| set_output_page_pin | — | |
| inspect_home_recent_tab | — | |
| configure_home_recent_tab | — | |
| list_workspace_views | — | |
| create_workspace_view | — | |
| get_workspace_view | — | |
| update_workspace_view | — | |
| archive_workspace_view | — | |
| list_knowledge_lists | — | |
| get_knowledge_rows | — | |
| get_knowledge_rows_by_ids | — | |
| get_knowledge_text | — | |
| create_knowledge_list | — | |
| update_knowledge_list_schema | — | |
| delete_knowledge_list | — | |
| upsert_knowledge_rows | — | |
| delete_knowledge_rows | — | |
| upsert_knowledge_text | — | |
| delete_knowledge_text | — | |
| query_kg_edges | — | |
| get_scoring_history | — | |
| get_workspace_credits | — | |
| get_workspace_credit_cost_drivers | — | |
| rolling-30-days | — | |
| rolling-7-days | — | |
| current | — | |
| previous-month | — | |
| all-time | — | |
| get_branding | — | |
| update_branding | — | |
| list_agents | — | |
| get_agent | — | |
| create_agent | — | |
| update_agent | — | |
| activate_agent | — | |
| pause_agent | — | |
| manage_agent_workflows | — | |
| delete_agent | — | |
| chat_with_agent | — | |
| list_agent_files | — | |
| get_agent_file | — | |
| upload_agent_file | — | |
| update_agent_file | — | |
| delete_agent_file | — | |
| message | — | |
| session_id | — |
구성
AGENTLED_API_KEY필수비밀Your AgentLed workspace API key (generate in Workspace Settings > Developer)
| 이름 | 설명 | 유형 |
|---|---|---|
| AGENTLED_API_KEY | Your AgentLed workspace API key (generate in Workspace Settings > Developer) | 필수비밀 |
자동 검사
2026년 11월 12일에 실행됨전체 보고서 →자동 검사를 통과했습니다. 이는 보안 감사가 아닙니다. 코드를 직접 읽고 서버에 필요한 최소한의 권한만 부여하십시오. 검사 방식
- 소스 저장소 연결 및 접근 가능통과
- 오픈 소스 라이선스 (OSI)통과
- 최근 1년 내 커밋 또는 릴리스통과
- 패키지 이름이 인기 패키지와 유사하지 않음통과
- 원격 엔드포인트가 HTTPS 사용검사되지 않음
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 모델에 대한 숨겨진 지침 없음통과
- 패키지 및 해당 종속성에 중요한 보안 권고 없음통과
README
GitHub에서 보기@agentled/mcp-server
The automation engine built for AI agents. Intelligent AI workflow orchestration with long-term memory, 100+ integrations, and unified credits.
What is Agentled?
Agentled is the automation engine built for AI agents. It gives Claude, Codex, Cursor, Windsurf, and any MCP-compatible client direct access to intelligent workflow orchestration, long-term memory, and 100+ integrations.
Three things make it different:
🧠 Long-Term Memory — A built-in Knowledge Graph stores insights across workflow executions. Your agents get smarter over time — they remember past research, lead scores, content performance, and business context.
⚡ Unified Credits — One API key, one credit system, 100+ services. No need to sign up for LinkedIn, email, scraping, AI models, or video generation separately. Connect once, use everything.
🎯 Intelligent Orchestration — AI reasons at every step. Workflows aren't just "if this then that" — they understand context, make decisions, and adapt to results.
See it in action
$ agentled create "Outbound to fintech CTOs in Europe"
Loading workspace context from Knowledge Graph...
✦ ICP loaded ✦ 3 prior campaigns ✦ 847 contacts in KG
Creating campaign with 3 workflows...
━━ Workflow 1: Prospect Research linkedin · hunter · clearbit
✓ LinkedIn: CTO + fintech + EU → 189 profiles
✓ Enriched via Hunter + Clearbit → 156 matched
✓ ICP scoring → 43 high-intent leads
━━ Workflow 2: Signal Detection web-scraper · crunchbase
✓ Job postings → 12 hiring devops
✓ Crunchbase → 8 recently funded
✓ Cross-match: hiring + funded → 5 hot leads
━━ Workflow 3: Outreach email · linkedin · kg
✓ Personalized emails from context
✓ LinkedIn requests with custom notes
✓ 43 leads saved to Knowledge Graph
Campaign saved. Scheduled: every 48h
Credits used: 720
→ https://www.agentled.app/your-team/fintech-cto-outbound
One prompt. Three workflows. LinkedIn enrichment, email finding, AI scoring, multi-channel outreach — all orchestrated, all stored in the Knowledge Graph for the next run.
Quick Start
claude mcp add --transport stdio --scope user agentled \
-e AGENTLED_API_KEY=wsk_... \
-- npx -y @agentled/mcp-server
--scope user registers the server in your user MCP config so it loads in every project (not only the repo where you ran the command). Use a distinct server name (e.g. agentled_my_workspace) if you add multiple workspaces. For team-shared config in git, use --scope project and .mcp.json instead (Claude Code MCP scopes).
Claude Code plugin (one-step install)
Prefer the plugin if you want the MCP server and the Agentled skill installed together. In Claude Code:
/plugin marketplace add Agentled/mcp-server
/plugin install agentled@agentled
Then set your API key in the shell Claude Code runs from:
export AGENTLED_API_KEY=wsk_...
Codex plugin (one-step install)
The same repository is a Codex marketplace. Install the Agentled plugin with:
codex plugin marketplace add Agentled/mcp-server
codex plugin add agentled@agentled
Then set AGENTLED_API_KEY=wsk_... in the shell that launches Codex and start a
new task. The plugin bundles the Agentled skills, starts the MCP server through
npx -y @agentled/mcp-server, and loads its lifecycle hooks from the standard
hooks/hooks.json path.
The plugin bundles the agentled skill (workflow-authoring guidance, namespaced agentled:agentled) and auto-starts the MCP server via npx -y @agentled/mcp-server. The same plugin directory carries both Claude Code and Codex manifests — one bundle, both hosts.
For Codex, the hook pack acts as in-session guidance around the CLI/MCP loop:
session start explains the Agentled/Codex business-loop split, prompt/tool hooks
add turn-level guidance when client needs, priorities, failures, or product gaps
appear, and stop hooks nudge implementation handoffs to include readiness,
validation, side effects, and next decision. Hooks do not store feedback, call
Agentled APIs, run automations, spend credits, or perform customer/workspace
writes. In Codex, run /hooks after installing or changing the plugin so the
local hook definitions are reviewed and trusted before they run.
Use Codex automations for outside-workspace FDE cadence such as Outlook/client
email follow-up, vendor replies, repo/build checks, and weekly operator reviews.
Use Agentled routines for Agentled workspace/runtime checks such as workflow
health, routine health, execution review, workspace summaries, and managed-agent
operations. Use submit_feedback_to_agentled or agentled feedback submit when
the user explicitly wants product feedback captured.
Pick one install path, not both. If you previously ran
claude mcp add agentled ...or--setup-skills, remove those before (or instead of) installing the plugin — otherwise you get two identical MCP server processes and the skill registered twice. Cleanup:claude mcp remove agentledand delete.claude/skills/agentled/(or~/.claude/skills/agentled/).--setup-skillsnow detects an installed plugin and refuses to double-register unless you pass--force.
To develop the plugin locally:
claude --plugin-dir ./plugins/agentled # load from source
claude plugin validate ./plugins/agentled # check manifest + structure
plugins/agentled/skills/is a generated mirror ofskills/(synced bypublish.sh) — editskills/agentled/SKILL.md, never the mirror.
Local development
Use the local built entrypoint when you want to test unpublished changes against a
local app. npx -y @agentled/mcp-server always uses the latest published npm package.
cd agentled-mcp-server
npm run build
claude mcp add --transport stdio agentled_local \
--env AGENTLED_API_KEY=wsk_... \
--env AGENTLED_URL=http://localhost:8080 \
-- node /absolute/path/to/agentsled-front/agentled-mcp-server/dist/index.js
Getting your API key
- Sign up at agentled.app
- Open Workspace Settings > Developer
- Generate a new API key (starts with
wsk_)
Why Agentled MCP?
One API Key. One Credit System. 100+ Services.
No need to sign up for LinkedIn APIs, email services, web scrapers, video generators, or AI models separately. Agentled handles all integrations through a single credit system.
| Capability | Credits | Without Agentled |
|---|---|---|
| LinkedIn company enrichment | 50 | LinkedIn API ($99/mo+) |
| Email finding & verification | 5 | Hunter.io ($49/mo) |
| AI analysis (Claude/GPT/Gemini) | 10-30 | Multiple API keys + billing |
| Web scraping | 3-10 | Apify account ($49/mo+) |
| Image generation | 30 | DALL-E/Midjourney subscription |
| Video generation (8s scene) | 300 | RunwayML ($15/mo+) |
| Text-to-speech | 60 | ElevenLabs ($22/mo+) |
| Knowledge Graph storage | 1-2 | Custom infrastructure |
| CRM sync (Affinity, HubSpot) | 5-10 | CRM API + middleware |
Workflows That Learn
Other automation tools start from zero every run. Agentled's Knowledge Graph remembers across executions — what worked, what didn't, what humans corrected. Scoring workflows can use compact row-level scoring_profile summaries and bounded scoring-memory retrieval so every run compounds on the last without dumping raw history into prompts.
Run 1: Investor scoring → 62% accuracy (cold start)
Run 5: → 78% (learning from IC feedback)
Run 12: → 89% (compound learning from outcomes, zero manual tuning)
Intelligent Orchestration
Unlike trigger-action tools, Agentled workflows have AI reasoning at every step. Multi-model support (Claude, GPT-4, Gemini, Mistral, DeepSeek, Moonshot), adaptive execution, and human-in-the-loop approval gates when needed.
Agent Teams
Agent Teams let you run multiple AI specialists in a single workflow step. Pick a preset and describe what you need — the team handles coordination, delegation, and synthesis.
"Add an Agent Team step that researches the company and produces an investment memo"
Six built-in presets cover the most common patterns:
| Preset | What it does |
|---|---|
research-and-summarize |
Specialists gather information, one synthesizes a summary |
analyze-and-recommend |
Multiple analysts evaluate options, produce a ranked recommendation |
generate-then-review |
A generator drafts content, reviewers critique and refine |
compare-options |
Specialists argue for competing options, coordinator arbitrates |
investigate-in-parallel |
Independent specialists explore different angles simultaneously |
review-and-improve |
Reviewers find issues, an editor applies improvements |
When creating Agent Team steps via MCP, include preset metadata so the step opens correctly in the builder:
{
"id": "analyze",
"type": "agentOrchestrator",
"name": "Agent Team",
"orchestratorConfig": {
"pattern": "supervisor",
"workers": [
{ "id": "researcher", "name": "Researcher", "systemPrompt": "Research {{input.company_url}} — team, funding, market position" },
{ "id": "analyst", "name": "Analyst", "systemPrompt": "Analyse the research. Identify risks and growth signals." }
]
},
"metadata": {
"agentTeamPreset": "research-and-summarize",
"agentTeamMode": "simple",
"agentTeamUxVersion": 1
},
"next": { "stepId": "milestone" }
}
Existing steps created with raw orchestratorConfig and no metadata continue to work — they open in advanced mode in the builder without errors.
Analytics vs ROI semantics
When describing workflow outcomes, keep these terms separate:
pipeline.analyticsConfig= business metrics (execution outcome stats shown in Business Metrics cards/charts).pipeline.metadata.roi= ROI assumptions/rollups (time saved and cost-value estimates).
If you update one without the other, name exactly what changed (e.g. "business metrics configured" vs "ROI assumptions configured").
CLI parity guard
The repository includes an automated parity guard so MCP tool additions do not silently drift from the CLI surface.
- Test:
__tests__/cli/cli-mcp-parity.test.ts - Docs:
docs/CLI_MCP_PARITY.md
Run it with:
yarn test:node -- cli-mcp-parity.test.ts
What Can You Build?
Lead Enrichment & Sales Automation
"Find fintech CTOs in Europe, enrich via LinkedIn + Hunter, score by ICP fit,
draft personalized outreach, save everything to the Knowledge Graph"
Content & Media Production
"Scrape trending topics in our niche, generate 5 LinkedIn posts with AI,
create thumbnail images, schedule publishing for the week"
Company Research & Intelligence
"Research this company from its URL — team, funding, market position, competitors.
Generate an investment memo. Store in KG for future reference."
VC Investor Matching (real case study)
"Match this startup against our 2,000+ investor database. Score by sector focus,
stage preference, check size, and portfolio synergy. Compare with last round's outcomes."
3,000+ profiles processed. IC-ready reports. Prediction vs outcome learning — accuracy went from 62% to 89% over 12 runs with zero manual tuning.
Built-in Skills And Integrations
Media Production: Video generation, image generation, text-to-speech, auto-captions, media assembly
AI Intelligence: Multi-model AI (Claude, GPT-4, Gemini, Mistral, DeepSeek, Moonshot, xAI), Knowledge Graph, feedback loops, scoring & analytics
Data & Integration: LinkedIn (search, enrich, post), email (send, personalize), web scraping, social publishing, CRM sync, document analysis, OCR
Available Tools
Use-case operating guides
When work starts from an existing workflow ID, call get_workflow first and
inspect useCaseContext. Then call get_use_case with the returned key or
workflow graph ID, and read any operatingGuides before answering
workflow-specific questions, running backfills, or editing live config. Missing
guide warnings mean the operating README is not attached yet and the context is
incomplete.
When work starts from a user's business goal rather than an existing workflow,
use How to Build Use Cases From User Goals.
It covers the external-agent lifecycle from bounded chat result to KG text/list
state, WorkspaceUseCase, workflows, approval queues, and home summary updates.
Workflows
| Tool | Description |
|---|---|
list_workflows |
List all workflows in the workspace |
get_workflow |
Get full workflow definition by ID, including useCaseContext when linked |
get_workflow_credits |
Get ledger-derived, period-labelled workflow credit usage; opt in to cost drivers with includeCostDrivers |
create_workflow |
Create a new workflow from pipeline JSON |
update_workflow |
Update an existing workflow (top-level scalars; for context/metadata prefer update_workflow_context) |
update_workflow_context |
Workflow-level analog of update_step — three explicit verbs (updates / replace / unset) on context.* and metadata.* paths, returns diff + warnings |
add_step |
Add a step with automatic positioning and next-pointer rewiring |
update_step |
Low-level deep-merge updates into a single step by ID |
replace_step_dictionary |
Merge keys into a dictionary path (fieldUpdates, responseStructure, fieldMapping) without dropping siblings |
replace_step_path |
Set one nested path while preserving siblings (e.g. renderer.config.layout) |
unset_step_path |
Delete one step path |
append_step_array_item |
Append one item to a step array (tools, integrations, …) |
remove_step_array_item |
Remove one array item by index or match |
remove_step |
Remove a step with automatic next-pointer rewiring |
delete_workflow |
Permanently delete a workflow |
validate_workflow |
Validate pipeline structure, returns errors per step |
publish_workflow |
Change workflow status (draft, live, paused, archived) |
export_workflow |
Export a workflow as portable JSON |
import_workflow |
Import a workflow from exported JSON |
Public Form Links
Public form links are the external intake surface for workflows with
context.executionInputConfig fields. Use them when people outside the
workspace need to submit a workflow form without signing in: inbound lead
forms, pitch deck submissions, referral forms, support intake, assessment
questionnaires, or any workflow whose first step is a manual/input trigger.
Do not use a public form link for internal child workflows. Child workflows
should use context.executionInputConfig.internal: true and be called from
another workflow with agentled.call-workflow.
| Tool | Description |
|---|---|
list_public_form_links |
List existing public form links for a workflow |
create_public_form_link |
Create and enable a public form link |
update_public_form_link |
Enable/disable a link or update limits, expiry, auto-share, and thank-you copy. To revoke external access, set enabled: false. |
Deletion is intentionally not exposed via the external API or MCP. To revoke a public form link, call
update_public_form_linkwithenabled: false. Permanent deletion requires an authenticated workspace member acting through the UI — destructive ops on the form-link surface are not granted to the public API key.
Typical agent flow:
1. get_workflow({ workflowId })
2. Confirm context.executionInputConfig exists and is not internal.
3. list_public_form_links({ workflowId })
4. If none exists, create_public_form_link({ workflowId, enabled: true })
5. Return the publicUrl to the user.
The public URL is /en/forms/{formLinkId}. On submit, Agentled validates the
form link, starts the workflow with the submitted input, records a
PublicFormSubmission, and increments submissionCount. Optional settings:
enabled: disable without deleting the link.expiresAt: ISO datetime expiry.submissionLimit: maximum accepted submissions.autoShare: when true, the public form status page can show generated results after completion. Use this only when the workflow output is safe for the submitter to see.shareExpiresInDays: expiry for auto-shared result links.successMessage: custom thank-you message after submission.
Internal-only Workflows
Mark a workflow as a child / sub-workflow that is only run via agentled.call-workflow from an orchestrator by setting context.executionInputConfig.internal: true. The UI then hides the Run button and replaces the manual run form with an info banner. Inputs are still validated and passed by orchestrators via executionInputData exactly as before — this is a UI guard, not a runtime restriction.
Use it for any workflow whose goal/description starts with "Internal sub-workflow", that ends in a return step, or that you only intend to invoke from another workflow.
{
"context": {
"executionInputConfig": {
"title": "Save Sourced Candidates",
"internal": true,
"fields": [{ "name": "candidates", "label": "Candidates", "type": "text", "required": true }]
}
}
}
Flip the flag via update_workflow_context — fetch first, merge locally, replace at the parent level (the merge-order trap from update_step applies here too — see docs/MCP_STEP_EDITING.md):
// 1. get_workflow → read context.executionInputConfig
// 2. local: { ...executionInputConfig, internal: true }
// 3.
{
"updates": { "context": { "executionInputConfig": {...full merged value...} } },
"replace": ["context.executionInputConfig"]
}
Agentled MCP 질문
Agentled MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --env 'AGENTLED_API_KEY=<YOUR_AGENTLED_API_KEY>' mcp-server -- npx -y @agentled/mcp-server를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Agentled MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Agentled MCP는 어떤 도구를 제공하나요?
107개 도구를 제공합니다. 예: list_workflows, get_workflow, get_workflow_credits, create_workflow, update_workflow.
Agentled는 다양한 서비스 통합을 어떻게 처리하나요?
단일 API key를 통해 LinkedIn, 이메일, 다양한 AI 모델 등 100개 이상의 서비스에 접근할 수 있는 통합 크레딧 시스템을 사용합니다.
Agentled의 메모리는 다른 자동화 도구와 무엇이 다른가요?
워크플로우 실행 전반에 걸쳐 인사이트를 저장하는 내장 Knowledge Graph를 갖추고 있어, agent가 과거의 조사 내용과 비즈니스 컨텍스트로부터 학습할 수 있습니다.