Kimi can help you explore ideas, review evidence and choose a next step from your experience, constraints and any current product knowledge. With a compatible MCP client, 1PC gives the assistant access to that saved state and the guidance for the task you choose.
This guide is for a technical solo founder who already uses Kimi. The practical connection path below is Kimi Code for VS Code. Provider documentation supports its remote HTTP MCP setup; a successful live 1PC connection still needs to be checked in your installed version.
Choose the Kimi surface before choosing a workflow
“Kimi” can mean a chat website, an editor assistant or a model used inside another client. The client determines which external tools and instructions the assistant can use. A model name alone does not establish MCP connectivity.
| Surface | Documented capability | What to do for 1PC |
|---|---|---|
| Kimi Code for VS Code | Remote HTTP MCP servers with optional OAuth. | Use the Kimi Code connection guide and verify access. |
| Kimi web | Plugins can include MCP and Skills; availability varies by surface and region. | Check the actual plugin and authorization path. This guide does not establish a 1PC marketplace listing. |
| A Kimi model in another app | Capabilities depend on the app hosting the model. | Check that app's remote MCP transport and authentication support before connecting. |
See the official Kimi Code customization guide and Kimi plugin overview for these surface differences. The 1PC MCP overview explains the product-side connection requirements.
Give the task a current product starting point
If you have no clear idea yet, begin with founder context and a question to investigate. Use a working product name to keep candidate directions and findings together. Useful product context is small enough to inspect and specific enough to change a recommendation. It includes the customer you chose, the problem you are trying to solve, evidence and its limits, current scope and your available time.
If your product already exists, start with its website, documentation and accepted decisions. Collection should identify what a source supports and what is missing. A polished homepage is evidence of the current offer, not proof that customers want a new feature.
In a connected client, enter 1PC's Product Owner flow before requesting domain work. It reads saved state, explains what already exists and helps resolve unclear reuse, reruns or changes that affect accepted choices. That makes “improve our landing page” a scoped product task rather than a fresh guess about the business.
A remote MCP connection supplies tools; it does not automatically install the native Product Owner skill. The setup guide includes an explicit entry request for hosts without that skill.
Connect the next action to its evidence and result
Keep the loop consistent: read state, choose a task, load relevant guidance, complete the authorized scope, then save and verify the result when requested. The assistant's research, editing and execution options depend on the tools actually available in the Kimi host.
- When you are unsure what to do next, use the weekly product review worksheet to compare actions against evidence and capacity.
- When you accept a feature scope, use the feature-launch marketing plan to connect the same customer problem to landing-page messaging, social content, an SEO angle and a focused channel test.
- When you have a repeatable checklist, create a private custom skill in 1PC. Product Owner can discover and load a published version with the relevant product context.
These guides own the detailed methods and templates. You can use them across compatible clients; the Kimi setup determines how you reach that work, not a separate set of product facts.
Work one bounded task through to a reviewed result
Consider the fictional Follow-up Board, a SaaS that helps freelance designers track unanswered proposals. The accepted audience is a solo designer, while an older landing-page draft emphasizes agencies. You want to correct that draft before deciding whether to expand the product.
Use 1PC for Follow-up Board. Enter Product Owner first and read
the saved customer decision, product scope and landing-page draft.
Explain their current state and any conflicts.
Draft a landing-page correction for the accepted freelance-designer
audience. Separate supported behavior from planned features.
Save the reviewed draft using the workflow's destination and verify it.
Suggest one relevant marketing follow-up; leave it as a suggestion.
This is an illustrative request, not a record of a completed Kimi run. A useful response would identify the audience conflict, load the available landing-page guidance, produce the correction and report the verified save. If the required sources or access are missing, it should explain the gap before claiming completion.
The related marketing idea can help you choose the next action. It does not authorize publishing content, contacting prospects or deploying a page. A request to inspect status alone stays read-only.
Start a fresh session from the saved work
Open a new conversation, reconnect the same 1PC account and select the same product. Ask Product Owner to read the saved landing-page draft and accepted customer direction before continuing. Verify that it reads the actual file rather than reconstructing the earlier conversation.
Only saved product knowledge, decisions and progress carry through this route. A chat-only decision, a temporary attachment or a running agent stays with its original host. The cross-AI product context guide explains what to save and how to check a continuation.
Your private method is separate from these product facts. Editing a custom-skill draft does not change its published version. Publish the new version deliberately, then ask the next task to use the intended method.
Check both providers' access before committing to a task
Kimi host access and 1PC prepaid usage are separate. Every 1PC User has the available workflow catalog and private workspace skills. Accepted private MCP calls consume Token Wallet credit. See current 1PC pricing.
Authorization also matters: read access does not grant permission to save. Discover the deployed tool catalog and account availability rather than assuming a page or model name grants a capability. The MCP documentation covers scopes, persistence and client verification.
Begin with one small connection and continuation check. Once the saved state is visible in a fresh session, choose the next product task from the work you actually have.
Connect Kimi to the product state you already have.
Follow the Kimi Code for VS Code setup, authorize 1PC and verify a small read/save/read-back task.
Set up 1PC in Kimi Code ↗