An MCP integration starts duplicating tool calls after a client reconnects. You spend an afternoon tracing requests, checking assumptions and testing possible fixes. The solution takes a few lines of code, but the investigation has taught you something that other developers might find useful. That could be the basis of a conference talk.
With the call for proposals (CFP) now open for AGNTCon + MCPCon North America 2027, it's a good time to look at the technical problems you've solved, the experiments you've run and the lessons you might be taking for granted.
Look for what you learned, not what you built
It's tempting to start with the biggest project you've worked on. But a project overview can cover so much ground that it's difficult to give an audience something they can use. A narrower experience might make a more interesting talk.
Perhaps you discovered that an agent's evaluation scores concealed a recurring failure. Maybe an MCP server behaved unexpectedly under load, or you found that a simpler workflow was more reliable than the multi-agent system you initially planned.
You don't need a breakthrough or a completely new technology. A result that surprised you, a trade-off you struggled with or an approach you abandoned can all make useful material.
Try looking back through recent pull requests, incident reports, experiments and team discussions. Which problems took longer than expected? Which decisions generated the most disagreement? What would you approach differently if you started again?
Find the part someone else can use
Once you've found a possible topic, narrow it to a question your experience can help answer.
"Building an agent platform" could become a talk about choosing between persistent and temporary memory. "Evaluating AI agents" might focus on detecting task failures that response-based checks miss.
A useful starting point is to identify four things:
- What were you trying to achieve?
- What happened that you didn't expect?
- How did you investigate or respond?
- What could someone facing a similar problem learn from it?
The last question matters. Your audience might use a different framework, model or infrastructure, but the reasoning behind a technical decision can still be relevant.
You don't have to claim that your solution is the best one, either. Explaining where it worked, where it didn't and what remained unresolved can make the experience more useful.
For community conferences such as AGNTCon, keep the focus on technical lessons rather than promoting a product. The CFP warns that sales and marketing pitches are almost always rejected.
Turn the experience into a proposal
Compare these two hypothetical abstracts for a talk about MCP integrations.
Before: Building reliable MCP integrations
A presentation exploring the challenges of implementing MCP servers, including reliability, error handling and best practices for production environments.
After: Handling repeated tool calls in an MCP integration
An MCP integration worked during testing, but repeated requests sometimes triggered the same action twice. I'll show how we reproduced the behavior, where we introduced checks to prevent duplicate actions, and the trade-offs involved when tools modify external state.
The second version gives the audience a clearer picture of the problem, what the speaker will demonstrate and what they might learn.
It also gives the speaker a manageable scope. Instead of trying to cover everything about MCP reliability, they can concentrate on one problem and the decisions involved in solving it.
You can use that approach with almost any technical experience. Start with what happened, identify what you can show, and make the takeaway clear.
Choose a format that suits the idea
Not everything needs to become a 25-minute presentation. A small discovery could work well as a lightning talk, while a working implementation might suit a live demo. If attendees need to configure, build or test something themselves, a workshop might be more appropriate.
AGNTCon + MCPCon North America 2027 accepts five-minute lightning talks and live demos, 25-minute presentations and 90-minute workshops, alongside panels and poster presentations.
Choose a format that lets you explain the lesson properly without stretching a narrow topic or trying to cover too much.
Let your experience show
The AGNTCon + MCPCon CFP asks submitters to explain what audiences will learn.
It also cautions that heavily AI-generated or templated submissions can lack the specificity reviewers need to assess a speaker's technical expertise.
That's worth considering when putting together any technical proposal. An LLM might help tidy an abstract, but the details that matter should come from your own work: the problem you encountered, the evidence you gathered, the choices you made and what you learned.
First-time speakers are encouraged to apply, and if you're unsure about your abstract, the organizers offer to help you with your proposal.
Submitting to AGNTCon + MCPCon
Your next conference talk might start with a bug report, an experiment that didn't work or a decision your team spent days discussing.
The AGNTCon + MCPCon North America 2027 CFP is open until January 18, 2027, at 11:59 PM PST. The conference takes place April 28–29, 2027, in San Francisco. The CFP includes suggested topics, submission formats and guidance on preparing your proposal.
Share
Author




