GITBOOK-652: change request with no subject merged in GitBook

This commit is contained in:
Simon Spencer 2025-06-23 22:09:32 +00:00 committed by gitbook-bot
parent c1aa6815e4
commit 362089a565
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
10 changed files with 53 additions and 6 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 45 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 98 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 104 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 96 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 48 KiB

View File

@ -18,7 +18,8 @@
* [Mounting a Snowflake Data Share](choose-your-flipside-plan/snowflake-data-shares/mounting-a-snowflake-data-share.md)
* [Earn](welcome-to-flipside/earn.md)
* [Community](<flipside-community/get-started (1).md>)
* [Flipside Growth MCP](welcome-to-flipside/flipside-growth-mcp.md)
* [Flipside Growth MCP](welcome-to-flipside/flipside-growth-mcp/README.md)
* [🪿 Goose Flipside MCP Getting Started Guide](welcome-to-flipside/flipside-growth-mcp/goose-flipside-mcp-getting-started-guide.md)
## Data&#x20;

View File

@ -20,14 +20,13 @@ A table is materialized as incremental via the model config. Flipside does this
```
* [`materialized`](https://docs.getdbt.com/reference/resource-configs/materialized) sets the type of model
* [`incremental_strategy`](https://docs.getdbt.com/docs/build/incremental-models#about-incremental\_strategy) determines the build approach. On Snowflake, the default is `merge` but you may also see `delete+insert`
* [`unique_key`](https://docs.getdbt.com/reference/resource-configs/unique\_key) is a required parameter, regardless of incremental or table, but is used in the `incremental_strategy` to identify records.
* [`incremental_strategy`](https://docs.getdbt.com/docs/build/incremental-models#about-incremental_strategy) determines the build approach. On Snowflake, the default is `merge` but you may also see `delete+insert`
* [`unique_key`](https://docs.getdbt.com/reference/resource-configs/unique_key) is a required parameter, regardless of incremental or table, but is used in the `incremental_strategy` to identify records.
When creating models with incremental materialization, we need to write an incremental logic within the model. It is important for the incremental logic to be based on `_inserted_timestamp` and not on the `block_timestamp`_._ This is important especially when the data encounters gaps on certain dates. This enables the model to heal itself because gaps are associated with `block_timestamp` and when they get-inserted later, they get captured by _`_inserted_timestamp`._
```sql
{% raw %}
{% if is_incremental() %}
{% if is_incremental() %}
WHERE _inserted_timestamp >= (
SELECT
MAX(_inserted_timestamp) :: DATE - 1
@ -35,6 +34,5 @@ WHERE _inserted_timestamp >= (
{{ this }}
)
{% endif %}
{% endraw %}
```

View File

@ -0,0 +1,48 @@
# 🪿 Goose Flipside MCP Getting Started Guide
{% hint style="success" %}
Current supported models: `claude-sonnet-4``gemini/gemini-2.5-pro``gemini-2.5-flash-preview-04-17`&#x20;
For this example we'll be using Anthropic's `claude-sonnet-4` model.&#x20;
{% endhint %}
#### Requirements before you get started
1. Either an Anthropic or Google Gemini API Key
2. A unique Flipside MCP URL and API Key.
1. Don't have one? [Request one here.](https://flipsidecrypto.xyz/fc/flipside-mcp-interest)
## Here's how to add the Flipside MCP with Goose
### ![:inbox\_tray:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/apple-medium/1f4e5.png) Download & Install Goose Desktop
1. Go to [https://block.github.io/goose/docs/quickstart](https://block.github.io/goose/docs/quickstart) and download Goose Desktop for your OS
2. Install and launch the application
### ![:gear:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/apple-medium/2699-fe0f.png) Configure LLM Provider
1. Open Goose and you'll be prompted to choose and configure a provider. \
&#x20;
<figure><img src="../../.gitbook/assets/Screenshot 2025-06-23 at 2.44.02PM.png" alt=""><figcaption></figcaption></figure>
2. Click on the provider you want to use. We'll be using Anthropic for this example.
3. Paste in your API key (this is where you will need to get an API key from one of the supported LLM providers).
<figure><img src="../../.gitbook/assets/Screenshot 2025-06-23 at 2.41.37PM.png" alt=""><figcaption></figcaption></figure>
### ![:robot\_face:](https://a.slack-edge.com/production-standard-emoji-assets/14.0/apple-medium/1f916.png) Add the Flipside MCP
1. Once the model is configured navigate to the Goose chat page.&#x20;
2. Click the Gear Icon in the top right corner and select 'Advanced Settings'
3. Under 'Extenstions' click 'Add custom extension'
1. Extension name: `flipsidemcp` (can be whatever you want but no spaces)
2. Type: `SSE`
3. Endpoint: _Your unique URL_
4. Timeout: `300000` \
<figure><img src="../../.gitbook/assets/Screenshot 2025-06-23 at 3.07.15PM.png" alt=""><figcaption></figcaption></figure>
4. Click 'Add Extension'
5. Click 'Back' and start playing around!&#x20;
Need inspiration on what to ask? See the[.](./ "mention") page for more details.