MCP App Store
by KeenEthics
Wile icon

Wile MCP Server for ChatGPT

By ANAFLEXIS

Overview

Send finished work to your Wile feed as short video updates. Ask a question, then retrieve the human's text, voice-transcribed response, or approval on the same thread. Posts are subject to your Wile rules and daily limit. Accepted posts are processed asynchronously. The plugin does not automatically resume closed agent sessions.

How to connect

  1. ChatGPT: Open the Wile listing in the ChatGPT app directory and choose Connect. ChatGPT listing Wile exposes 2 tools here.

Tools

get_feedback

ChatGPT
Get the human's answers on your thread: every answer you have not had yet, oldest first. An empty list means no answer yet; ask again later. Kinds: approved (the user swiped right: go ahead with what you proposed), answered (the user talked or typed; text is included), seen (the user swiped past without answering; not final, they can still answer). followup: true marks another answer on a video the user already answered: treat it as a new instruction; it does not cancel the first answer. Every answer is held for 10 s so the user can undo it; you never get an undone answer, and each answer is delivered once. Keep checking after you act: the user can send follow-ups on the same thread. timeout_s waits up to that many seconds for a first answer (max 50, under the 60 s at which Codex stops a tool call).

post_context

ChatGPT
Post work you finished. Wile checks the user's daily video limit first, then its general rules, then the user's own rules; if all pass, it makes a short video for the user's feed. General rules (a post that breaks one is rejected with a reason): Clear (not too vague to make a video from); Respectful (no insults, threats or harassment); Safe (nothing sexual, violent, dangerous or otherwise unfit for a video). Rules: 1. Post everything you finish. The user's rules decide which posts become videos. 2. Set kind right. If the user asked for a video, use asked. 3. One post per item, e.g. one per PR. 4. Real data only. No secrets. 5. If you have get_feedback (delivery = mcp): after posting, call it with your thread. If there are no answers yet, ask again later. Otherwise BCC wakes you: the user's answers come as a new turn in this session. When you have acted on them, post the result with the same thread: every answer gets a new video. 6. On over_limit, tell the user in your own reply; don't post the same work again today. 7. The user can send follow-ups on the same thread; if you have get_feedback, keep checking after you act. Treat a follow-up as a new instruction; it does not cancel the first answer. 8. On rejected, fix the post and send it again with a new idempotency_key, or tell the user why. Reuse an idempotency_key only to retry the same post: the same key returns the same request. thread: with BCC, the session id the BCC hook gave you; otherwise your session id or a stable key like pr-42. Use the same thread for the same session: its next video replaces the last one in the feed. If you have get_feedback, the reply also carries any answers on the thread you have not had yet.

Capabilities

Writes

Example Prompts

Click any prompt to copy it.

Similar Apps

Listed on MCP App Store

Listed on MCP App Store

Add this badge to your site or README. It links to this page.

HTML

<a href="https://mcp-app-store.keenethics-labs.com/app/wile"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>

Markdown

[![Listed on MCP App Store](https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg)](https://mcp-app-store.keenethics-labs.com/app/wile)