AgentLater MCP server
2026년 11월 14일 커밋AI 에이전트가 HTTP 요청을 예약하고, 작업 완료 여부를 폴링하며, 이후 세션에서 결과나 웹훅을 가져올 수 있도록 지원합니다.
다른 이름 thachp/agentlater
- 스타
- 0
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 1.0.0
- 마지막 커밋
- 2026년 11월 14일
- 라이선스
- MIT
AgentLater MCP란?
AI 에이전트가 HTTP 요청을 예약하고, 작업 완료 여부를 폴링하며, 이후 세션에서 결과나 웹훅을 가져올 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
AgentLater MCP server 정보
자율 에이전트를 구축하는 개발자는 AgentLater를 사용하여 활성 채팅 세션 외부에서 발생하는 HTTP 요청을 예약할 수 있습니다. 이 hosted MCP server를 사용하면 에이전트가 백그라운드 작업을 트리거하거나, 작업 완료를 위해 폴링하거나, 웹훅을 수신하고 이후 세션에서 결과를 가져올 수 있습니다. 사용자 세션을 계속 열어두지 않고도 15분 후에 보고서를 생성하는 것과 같이 시간 지연 작업이 필요한 에이전트를 위해 설계되었습니다.
이 서비스를 사용하려면 원격 streamable HTTP 및 MCP OAuth를 지원하는 MCP client를 게이트웨이 URL에 연결하십시오. 인증은 수동 API 키 대신 표준 OAuth 흐름을 통해 처리됩니다. 연결되면 에이전트는 schedule_http, queue_http, create_cron과 같은 도구를 사용하여 작업을 관리할 수 있습니다. 또한 시스템은 read_inbox 및 ack_inbox를 통해 수신된 결과를 처리할 수 있는 인박스를 제공합니다. 체험판 기간에는 7일 동안 1,000회의 전달 시도가 포함되며, 사용자는 set_secret 도구를 사용하여 자격 증명을 안전하게 관리할 수 있습니다.
활용 사례
- 1지연된 백그라운드 작업 예약에이전트가 특정 지연 시간 후에 실행되도록 웹훅으로 POST 요청을 예약할 수 있습니다.
- 2장기 실행 작업 완료 폴링에이전트가 상태 URL을 모니터링하여 특정 작업이 완료될 때까지 기다릴 수 있습니다.
- 3새 세션에서 결과 가져오기에이전트가 인박스를 확인하여 이전 HTTP 전달 결과를 읽을 수 있습니다.
- 4예약된 작업 관리 및 재시도개발자가 도구를 사용하여 특정 작업을 검사, 중지 또는 재시도할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
AgentLater MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 AgentLater MCP 설치
$ claude mcp add --transport http agentlater https://gateway.agentlater.io/mcpCursor에 AgentLater MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"agentlater": {
"url": "https://gateway.agentlater.io/mcp"
}
}
}VS Code에 AgentLater MCP 설치
.vscode/mcp.json
{
"servers": {
"agentlater": {
"type": "http",
"url": "https://gateway.agentlater.io/mcp"
}
}
}VS Code CLI에 AgentLater MCP 설치
$ code --add-mcp '{"name":"agentlater","type":"http","url":"https://gateway.agentlater.io/mcp"}'Codex에 AgentLater MCP 설치
$ codex mcp add agentlater --url https://gateway.agentlater.io/mcpCodex config.toml에 AgentLater MCP 설치
~/.codex/config.toml
[mcp_servers.agentlater] url = "https://gateway.agentlater.io/mcp"
Gemini CLI에 AgentLater MCP 설치
$ gemini mcp add -s user --transport http agentlater https://gateway.agentlater.io/mcpGemini settings.json에 AgentLater MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"agentlater": {
"url": "https://gateway.agentlater.io/mcp",
"type": "http"
}
}
}자동 검사
2026년 11월 15일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능thachp/agentlater is public and reachablegithub.com/thachp/agentlater ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-14github.com/thachp/agentlater ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
GitHub에서 보기AgentLater
Let an AI agent make an HTTP request later, and check whether it happened.
AgentLater is a hosted Model Context Protocol (MCP) server for agents that need to schedule HTTP work, wait for a job, or retrieve results in a later session. It sends requests and records delivery outcomes; it does not run the agent itself.
What agents can do
| Need | Tools |
|---|---|
| Send a request later or in the background | schedule_http, queue_http (optionally serialize related requests in a named queue) |
| Repeat a request or poll until a job finishes | create_cron, watch_http |
| Receive webhooks and read results in a later session | create_hook, read_inbox, ack_inbox |
| Inspect, stop or retry work | get_task, list_tasks, cancel_task, redrive_task |
| Use credentials or trigger an agent workflow when results arrive | set_secret, set_wake |
See the full tool reference for arguments, limits and delivery semantics. A wake URL must belong to something that can start an agent run; inbox events alone do not resume a chat.
Connect an MCP client
Use a client that supports remote Streamable HTTP and MCP OAuth. Add a remote server or custom
connector named agentlater with this URL:
https://gateway.agentlater.io/mcp
For clients using an mcpServers JSON configuration with HTTP transport, the configuration is:
{
"mcpServers": {
"agentlater": {
"type": "http",
"url": "https://gateway.agentlater.io/mcp"
}
}
}
Configuration formats vary by client; use its remote-server settings if it does not accept this shape. The endpoint and transport are also declared in server.json.
Authentication: complete the OAuth flow opened by your client and click Connect on the
AgentLater consent page. There is no account to create or API key to paste into the configuration;
the client manages OAuth tokens. Each approved connection owns a separate project and trial.
Call create_project once after connecting (calling it again returns the same project): the trial
includes 1,000 delivery attempts for 7 days. Use get_project to inspect the balance and get_payment_link
when more attempts are needed.
For Claude Code, you can instead install the plugin, which includes the hosted server configuration and a skill for using the tools:
/plugin marketplace add thachp/agentlater
/plugin install agentlater@agentlater
See the plugin README for installation and migration details. Autonomous integrations can also use Agent Auth at the gateway; that identity and its project are separate from a hosted MCP connection.
A2A
An agent that speaks the Agent2Agent protocol (version 1.0,
JSON-RPC) can schedule one-off deliveries and read, list and cancel them, signed in with Agent Auth and no
human login. Start from the Agent Card at https://gateway.agentlater.io/.well-known/agent-card.json.
# in a checkout, after npm ci
node apps/gateway/examples/a2a-client.mjs https://gateway-staging.agentlater.io
a2a-client.mjs is a complete client in one file: it reads the Agent
Card, registers, makes its project, schedules a delivery and polls it to its end. Outside a checkout, copy the file and
npm install @a2a-js/sdk@1.3.0 @auth/agent@0.6.2. It keeps its keys in
~/.agentlater/ (mode 0600). The auth sequence, payload schema, task states, errors and what is not offered
through A2A (crons, watches, hooks, secrets, payments, streaming, push notifications, callbacks, lanes) are in
the A2A docs and PRODUCT.md.
Example: trigger a background job through a webhook
A common use is calling your application's job endpoint after a delay—for example, generating an export in 15 minutes without keeping the agent session open.
After connecting, ask your agent:
Create my AgentLater project, then POST to my export webhook in 15 minutes with
{"report": "daily-sales", "format": "csv"}. Use my stored webhook token, capture the response, and put the delivery result in my inbox.
The agent calls create_project with {}. If the endpoint requires a bearer token, first call
set_secret with these arguments, replacing the placeholder with your endpoint's actual token
and the host with your own:
{
"name": "WEBHOOK_TOKEN",
"value": "<your-webhook-token>",
"allowed_hosts": ["api.example.com"]
}
Then call schedule_http with the following arguments. Replace the example URL with your own
public HTTPS job endpoint. body is a JSON-encoded string, not an object.
{
"url": "https://api.example.com/jobs/export",
"method": "POST",
"headers": {
"Content-Type": "application/json",
"Authorization": "Bearer {{secret:WEBHOOK_TOKEN}}"
},
"body": "{\"report\":\"daily-sales\",\"format\":\"csv\"}",
"delay": "15m",
"idempotency_key": "daily-sales-export-001",
"capture": true,
"callback_url": "inbox"
}
Use a new idempotency_key for each intended job; reusing the same key and request returns the
original task. Your endpoint should also deduplicate deliveries using RunLater-Task-Id because
delivery retries can reach it more than once. For an endpoint without authentication, omit the
secret setup and the Authorization header.
Save the returned task_id and inspect it with get_task({"task_id": "<returned task_id>"}).
In a later session, call get_project with {}, then read_inbox with {} if inbox_unread
is above zero. After handling the events, call ack_inbox({"up_to": 1}), replacing 1 with the
last seq you handled. These are MCP tool names and argument objects, not shell commands.
No public callback URL is needed to receive the delivery report in the inbox. If the endpoint
returns 202 Accepted, that confirms it accepted the job; use watch_http on its status URL
when you also need to wait for the export to finish.
Delivery is at least once; succeeded means the destination returned HTTP 2xx. Destinations must
be public HTTPS URLs, not localhost or private IP addresses. For authenticated requests, store the
credential with set_secret and use {{secret:NAME}} in a header instead of pasting it into a request.
Limits and troubleshooting
- Schedule at most 7 days ahead. Cron expressions use UTC and run at most hourly; watches poll every 5 minutes to 24 hours. Captured responses keep the first 16 KiB of the body for 7 days after the task finishes.
project_not_found: callcreate_projecton the current connection before scheduling.budget_exhaustedortrial_expired: inspectget_projectand useget_payment_linkfor more attempts. Each delivery attempt, poll and URL callback attempt consumes budget; inbox delivery is free.- Connection or sign-in fails: confirm the URL ends in
/mcpand the client supports both Streamable HTTP and OAuth. A client limited to local stdio servers needs a supported bridge; see the Agent Auth bridge configuration. - No result yet: inspect
get_taskwith the returnedtask_idfor its status and attempt history. Read the inbox using the same connection that scheduled the task; a new connection has a separate project.
Documentation and compatibility
AgentLater was formerly RunLater. Existing runlater plugin connections retain their own projects;
installing the agentlater plugin creates a separate connection rather than moving existing work.
Some internal package names and delivery headers (such as RunLater-Task-Id) retain the old name
for compatibility.
The specs are PRODUCT.md (what it does), ARCHITECTURE.md (how it's built) and DESIGN.md (how it should feel, to agents and to people). The pre-rebuild implementation was removed at cutover; it is in git history before this change.
Layout
| Path | What | Stack |
|---|---|---|
apps/api |
Private task API: ledger, scheduling, delivery | Rust · workers-rs |
apps/gateway |
Public entry for agents: Agent Auth, capabilities, MCP, A2A | TypeScript Worker |
apps/web |
agentlater.io landing, docs and payment page | Next.js · OpenNext |
apps/receiver |
Staging-only fixture the journey and the A2A run deliver to | TypeScript Worker |
crates/core |
Task domain, no Cloudflare deps | Rust |
crates/egress |
Destination policy and request signing | Rust |
packages/contracts |
Capability definitions, and the OpenAPI contract between gateway and API | TypeScript · OpenAPI 3.1 |
packages/tsconfig |
Shared TypeScript config | |
plugins/agentlater |
Claude Code plugin: the hosted MCP server and an agentlater skill |
Markdown · JSON |
plugins/runlater |
The old plugin, deprecated and frozen so existing installs keep working | Markdown · JSON |
Everything deploys to Cloudflare Workers, with staging and production environments in each app's wrangler.jsonc (apps/receiver has staging only); see docs/DEPLOY.md.
Develop
Requires Rust (pinned in rust-toolchain.toml), Node 22+, and cargo install worker-build --version 0.8.7 --locked.
npm install
cargo test && npm run typecheck && npm test
Every check CI runs, in one command (-- --fast skips the e2e suites):
npm run verify
The rules the code keeps, and the lints that enforce them, are in CODING_STANDARDS.md.
npm run dev -w @runlater/gateway
npm run dev -w @runlater/web
License
The code is MIT. Using the hosted service at agentlater.io is covered by its Terms of Service and Privacy Policy.
AgentLater MCP 질문
AgentLater MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http agentlater https://gateway.agentlater.io/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
AgentLater MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
AgentLater의 체험판 제한은 무엇인가요?
체험판에는 7일 동안 1,000회의 전달 시도가 포함됩니다.
인증이 필요한 HTTP 요청에 secret을 사용할 수 있나요?
네, set_secret 도구를 사용하여 자격 증명을 저장하고 {{secret:NAME}} 구문을 사용하여 헤더에서 참조할 수 있습니다.
작업을 최대 얼마 전까지 예약할 수 있나요?
최대 7일 전까지 작업을 예약할 수 있습니다.