Adrian Cole
89 lines
4.1 KiB
Markdown
89 lines
4.1 KiB
Markdown
---
|
|
title: Pieces for Developers Extension
|
|
description: Add Pieces for Developers MCP Server as a goose Extension
|
|
---
|
|
|
|
import Tabs from '@theme/Tabs';
|
|
import TabItem from '@theme/TabItem';
|
|
import YouTubeShortEmbed from '@site/src/components/YouTubeShortEmbed';
|
|
import GooseDesktopInstaller from '@site/src/components/GooseDesktopInstaller';
|
|
import CLIExtensionInstructions from '@site/src/components/CLIExtensionInstructions';
|
|
|
|
<YouTubeShortEmbed videoUrl="https://www.youtube.com/embed/V8zp9m9__t4" />
|
|
|
|
This tutorial covers how to add the [Pieces for Developers MCP Server](https://docs.pieces.app/products/mcp/get-started?utm_source=goose&utm_medium=collab&utm_campaign=mcp) as a goose extension to enable interaction with your Pieces Long-Term Memory.
|
|
|
|
## Configuration
|
|
|
|
1. Download [PiecesOS](https://pieces.app/)
|
|
|
|
2. Enable [Long-Term Memory Context](https://docs.pieces.app/products/quick-guides/ltm-context) in PiecesOS
|
|
|
|
<Tabs groupId="interface">
|
|
<TabItem value="ui" label="goose Desktop" default>
|
|
<GooseDesktopInstaller
|
|
extensionId="pieces"
|
|
extensionName="Pieces for Developers"
|
|
description="Provides access to your Pieces Long-Term Memory. You need to have Pieces installed to use this."
|
|
command="uvx"
|
|
args={["--from", "pieces-cli", "pieces", "--ignore-onboarding", "mcp", "start"]}
|
|
/>
|
|
</TabItem>
|
|
<TabItem value="cli" label="goose CLI">
|
|
<CLIExtensionInstructions
|
|
name="Pieces"
|
|
description="Provides access to your Pieces Long-Term Memory"
|
|
type="stdio"
|
|
command="uvx --from pieces-cli pieces --ignore-onboarding mcp start"
|
|
/>
|
|
</TabItem>
|
|
</Tabs>
|
|
|
|
## Example Usage
|
|
|
|
Let's use the Pieces for Developers MCP server to generate a status update for a standup meeting based on your activities on the previous day.
|
|
|
|
### goose Prompt
|
|
|
|
```
|
|
I need a status update for what I was using yesterday. Create a report with 5 bullet points based off the most important activities, and give each one a brief description.
|
|
```
|
|
|
|
### goose Output
|
|
|
|
```
|
|
Here's a report summarizing your key activities from yesterday, based on the most important interactions and applications you were using:
|
|
|
|
1. Code Development with goose:
|
|
|
|
Activity: You worked on integrating MCP servers into the goose CLI, making enhancements to handle extensions via schema URLs.
|
|
Description: This task involved modifying code and testing new integrations to support advanced functionalities. It also included interactions with the goose community on Discord for feedback and troubleshooting.
|
|
|
|
2. Documentation Updates:
|
|
|
|
Activity: You updated and managed documentation related to the goose project and MCP integrations.
|
|
Description: This involved preparing documentation for new features, including usage guidelines and technical details, aiding in the improvement of user experience and technical instructions.
|
|
|
|
3. Community Interaction on Discord:
|
|
|
|
Activity: Engaged with the Block Open Source Community to discuss project developments and potential collaborations.
|
|
Description: You actively participated in community discussions, exchanging insights on project enhancements, and exploring collaborative opportunities with other developers and contributors.
|
|
|
|
4. Managing and Testing Extensions:
|
|
|
|
Activity: You focused on testing and managing various extensions through the goose platform.
|
|
Description: This included configuring and validating different extensions, ensuring their compatibility and functionality, and incorporating feedback from testing.
|
|
|
|
5. Content and Integration Planning:
|
|
|
|
Activity: Planned integration workflows for MCP and documented their use cases.
|
|
Description: You worked on strategies for implementing MCP integrations effectively, involving planning sessions to optimize future project deployments and align them with user requirements and project objectives.
|
|
|
|
These activities demonstrate a productive day with a focus on development, collaboration, and content management within your technical community.
|
|
```
|
|
|
|
|
|
:::tip
|
|
For more examples of prompts you can use with the Pieces for Developers MCP Server, see the [Pieces MCP prompting guide](https://docs.pieces.app/products/mcp/prompting?utm_source=goose&utm_medium=collab&utm_campaign=mcp).
|
|
:::
|